This patchset is adds a new path grouping policy that can be used with ALUA devices. The goal is to avoid the temporary incorrect path groupings that can happen when paths change priorities. There is one thing that I'm not sure of. Is there any possiblity of a path device changing the target port group it belongs to while it use? If so, then we would need code to check for this and reload the device if it occurs. Benjamin Marzinski (5): libmultipath: add group_by_tpg path_grouping_policy libmultipath: don't copy pgpolicy string in get_pgpolicy_name libmultipath: add ALUA tpg path wildcard multipath-tools tests: add tests for group_by_tpg policy libmultipath: add "detect_pgpolicy" config option libmultipath/config.c | 2 + libmultipath/config.h | 2 + libmultipath/configure.c | 1 + libmultipath/defaults.h | 1 + libmultipath/dict.c | 17 ++- libmultipath/discovery.c | 1 + libmultipath/hwtable.c | 1 + libmultipath/libmultipath.version | 10 +- libmultipath/pgpolicies.c | 42 ++++--- libmultipath/pgpolicies.h | 6 +- libmultipath/print.c | 9 ++ libmultipath/prioritizers/alua.c | 1 + libmultipath/propsel.c | 50 +++++++- libmultipath/propsel.h | 1 + libmultipath/structs.c | 1 + libmultipath/structs.h | 10 ++ multipath/main.c | 1 + multipath/multipath.conf.5 | 16 +++ tests/pgpolicy.c | 201 ++++++++++++++++++++++++++++++ 19 files changed, 338 insertions(+), 35 deletions(-) -- 2.17.2 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
