> backwards compatible with older kernels.  New kernels seeing a '0' in
> that spot would simply pick 'fifo' as before.  One question is whether
> to use 0,1,2,3 to encode the strategy, or to use letters, or whatever.
> But that's just a minor implementation detail.

considering the random garbage we saw in component labels when
adding > 2TB support, i don't trust that we won't see anything
with some garbage in this new place.

i wonder if we need to really version this properly 8-/


.mrg.

Reply via email to