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

[WIP] CA-192760: use noop scheduler for multipath devices #293

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

germanop
Copy link
Contributor

Patch not ready to be pushed.
The following is pending:

  • Check if current behaviour (we do set this in storage manager) is really broken. The fact
    that a slave device is set with an elevator different than the multipath dm devices does not necessarily
    mean the kernel is taking that elevator really into account
  • We need a better way to understand locally attached and root devices
  • We could add a check for non rotational disks

We need to ensure we use noop IO scheduler for multipath devices
and non local devices.

We were used to do that in the storage manager but for devices
going offline and added back this is not possible, becasue
SM is not running all the time.

This patch ensures the noop scheduler is set for specific devices
and this setting is preserved even when SM is not running
or when SM is not managing multipath (a potentially
upcoming feature).

Whit this rule, we use noop for any multipath device or any
block device that is not on the ATA bus (a very weak decision
rule to get an idea of locally attached devices).

Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
A decorator for deprecated functions has been created.
Deprecation is this case means replacing them with a no-op
function and a warning message.

Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
CA-192760: use noop IO scheduler for specific device types

We need to ensure that a noop scheduler is used for the following
devices:
- non rotational disks (e.g. SSDs)
- multipath devices (we assume they have a clever controller if
  many paths exist)
- remote arrays

In the latter case we are not sure the chosen rule is always
doing the right thing.

We were used to do that in the storage manager but for devices
going offline and added back this is not possible, because
SM is not running all the time.

This patch ensures the noop scheduler is set for specific devices
and this setting is preserved even when SM is not running
or when SM is not explicitly managing multipath (a potentially
upcoming feature).

Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
@germanop germanop changed the title CA-192760: use noop scheduler for multipath devices [WIP] CA-192760: use noop scheduler for multipath devices Jul 13, 2016
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.

None yet

1 participant