Skip to content
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

Expansion of policy scripting #70

Merged
merged 3 commits into from
Jul 10, 2018
Merged

Expansion of policy scripting #70

merged 3 commits into from
Jul 10, 2018

Conversation

nhorman
Copy link
Member

@nhorman nhorman commented Jul 10, 2018

This feature enhances our policy script feature. Currently irqbalance has the ability to use a single policy script, which must contain the logic to properly handle/ignore all devices, which is less than ideal. This feature enhances policyscripting to allow for a directory to be specified that holds multiple scripts, that can control individual devices. The idea being that if a IHV creates a device that needs special irqbalance policy, they can submit a script for inclusion that detects only their device and handles it accordingly.

Its been deprecated for a few years and releases now, its time to reap
this option

Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Latest gcc caught some errors in our string copying routines.  Fix those
up

Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
The policyscript directive allows for the specifcaion of a single script
to define policy for all hardware on a system, which is good as a
site/host specific utility, but it makes for difficult work in the event
that vendors wish to provide guidance for only their own hardware (i.e.
if vendor A wants certain hardware to follow affinity_hinting without
affecting other hardware).  To manage this, lets enhance policyscript to
allow the specification of an entire directory, to which multiple
scripts can be added.  Semantics for this new directory feature are the
same as for the single script case, except that the script exit codes
have additional meaning:

exit code 0 - the script indicates that the referenced irq relates to a
device that this script recognizes and further script processing should
stop

exit code 1 - the script indicates that the referenced irq does not
relate to a device the script recognizes, and script processing should
continue

exit code >2 - the script indicates an error has occured, and any output
from it should be ignored, script processing should continue

Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
@nhorman nhorman merged commit c63839c into master Jul 10, 2018
@nhorman nhorman deleted the affinity branch July 11, 2018 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant