-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor *_user_test_runner.sh to run in containers #36
Comments
@xinzhanz can you please take a look? |
@mythi If remove cleanup, start_dsa, enable_wqs, this scripts won't work. The purpose is to provide a script which can show it runs well. I don't think it is good to configure DSA/WQs out of the runner. |
@xinzhanz no need to remove them but make them run conditionally. one flow could be the user adds: |
I prefer --skip-config to skip enable/disable devices in scripts. So need to guarantee the wqs in /dev/dsa are all enabled devices for user. |
Sounds OK. Maybe you can reuse this code from our patch:
things to be aware of with containers:
|
v1-0001-accel-config-test-provice-skip-config-to-run-dsa-.patch |
@hj-johannes-lee can you help checking this patch as part of your work |
Great! I will make a patch for review. Thanks @hj-johannes-lee @mythi . |
can we have the same for both IAA and DSA? |
I think there is a potential issue about this implementation, use my local env. as an example, In iaa_user_test_runner.sh, it's necessary to check whether an op is valid and different op has different command line parameters, so each op has its own commands. There are dozens of command lines leading by iaa_test need to be modified and each of them need to loop in all the enabled devices and work queues. As a tool for common use, I think "--skip-config" and accepting enabled devices and work queues are not a good behave for the script iaa_user_test_runner.sh. How about you guys opinions? |
our need is fairly simple: run by using the devices that available (in containers, can be a subset of what enabled on the host) but don't do any WQ (re-)configuration and don't assume any fixed WQ id. the tests scripts have proven to be useful because of their coverage but unfortunately requires patching to be useful in containerized environments. that's the reason for this issue. |
Do you need a script that can enumerate and run on all enabled work queues? I mean, for example,
|
It's not important but as far as I can think of, this would be straightforward with a loop for all devices detected. |
What is the status of this issue? Is there any patch that needs to be merged? |
v1-0001-accel-config-test-Add-parameter-for-specifying-de.patch |
@hj-johannes-lee would you be able to help? |
@mythi Let me do today or at least by tomorrow.! :) |
Sorry for late message. I was struggling with finding a system that has iaa and then with kernels. |
We did not test with all platforms. This is problematic still: idxd-config/test/iaa_user_test_runner.sh Lines 502 to 514 in 6c3261f
|
@zhangl6 can you please take a look? |
I'd like to be able to use these scripts in containers without patching in our end-to-end testing for Kubernetes.
Essentially for containers, the flow is that the node admin has configured the WQs, and the tests are run by passing
--device /dev/dsa/wq0.0
etc.The text was updated successfully, but these errors were encountered: