Hardsector size support in 2.4 and 2.5

[Mark Peloquin]

I was wondering if 2.5 will *really* support different hard sector
sizes. Today the hardsect array in the kernel seems to serve
little purpose. Drivers fill it in, but then what? It does not appear
to be used in any io path computations as illustrated by code
in submit_bh and generic_make_request which use a few
hardcoded shifts by 9 when dealing with sector sizes.

Is the hardsect array on the way *in* or the way *out* of the
kernel? Will 2.5 take the real hardsector value into account?
Or can we expect everything to be handled in 512 byte
multiples  (as we do today)?

Thanks.
Mark Peloquin