Closed velurimithun closed 5 months ago
Thank you for this nice PR!
I agree that passing any --damos_*
without --damos_action
makes no sense. However, this change will force --damos_action
even if no --damos_*
option is given. That is, say, damo tune --monitoring_intervals 5ms 200ms 2s
should be a legal command, but this change will give a unnecessary error to the user. Could we handle such cases?
Thanks for your review @sj-aws . I've now updated the commit to check for damo_action
only when any damo_*
option is present in input args.
Moving further, in order to avoid these situations (where other functionalities can break) I'll run all the tests before raising PR.
[root@ip-172-31-36-123 damo]# ./tests/run.sh
PASS unit test_damo_records.py
PASS unit test_damo_scheme_dbgfs_conversion.py
PASS unit test_damo_schemes_input.py
PASS unit test_damo_show.py
PASS unit test_damon.py
[...]
PASS start_stop sysfs stop
PASS start_stop
PASS ALL
[root@ip-172-31-36-123 damo]#
Looks good to me, thank you for this PR!
Description of changes:
Check if user has provided any 'damos_action'. Without 'damos_action', tune will ignore damos_quotas and damos_quota_goal.
Throws error messages if no 'damos_action' is specified in tune cmd.
Env:
Before patch:
After patch:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.