[s]sd-config-list version 2 and retry count tuning [PSARC/2007/505 FastTrack timeout 09/11/2007]

[Bill Sommerfeld]

The property encoding being revised seems particularly error prone --
you need to define a bitmask and then an sequence of values where bit N
of the bitmask tells the driver to look at value N in the sequence.

If you're going to revise the encoding to be consistent across
platforms, it also seems like it might be a good opportunity to make it
less administrator-hostile in other ways.

On Tue, 2007-09-04 at 07:56 -0700, Mark Carlson wrote:
> Those bits that only exist in version 1 are obsolete in version 2.

we generally closely review proposals which remove functionality or
declare it obsolete; can you enumerate the set of removed bits and
explain why it's appropriate to remove each tunable?

Will the removed bits be turned into no-ops, or will they continue to be
settable via a version 1 encoding?

> For a given vender ID and
> product ID string, if both version 1 and version 2 are found,
> version 2 will take effect. 

I'm missing how that's possible given the encoding described in this
case and in 2001/692 -- can you show an excerpt of [s]sd.conf syntax
showing this ambiguity?  

					- Bill