On Wed, Nov 27, 2013 at 10:54:04AM +0900, Akira Hayakawa wrote: > The only essential property of the table output is that it can > recreate the same device? There is a further constraint. Userspace often uses the optimisation of comparing the table line output from the existing device with a proposed new table line to determine whether or not the table has changed and needs to be reloaded. For simplicity, this can be a string comparison. As such, the output table line that corresponds to any particular internal table state should always be defined uniquely, particularly if there is more than input table line that leads to that same table state. Typically this means one of two things: EITHER arbitrary choices (e.g. the order of supplied arguments in an unordered list; device references) are preserved between the input and output table lines OR (normally the better option) the output is always presented in the same standard format regardless of the input (e.g. unordered parameter lists are output in a defined order). This means that userspace code that is aware of the table output definition can choose to provide input in an exactly matching form, but the casual user is not inhibited by such arbitrary restrictions. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
