Andrew> Sounds OK to me for 2.5.
Will you make the change then? I'd appreciate that.
Andrew> For 2.4, a 32-bit b_size would push sizeof(buffer_head) from
Andrew> 96 up to 100 bytes, which does not pack as well into the
Andrew> slab. This would be an intensely unpopular move. So you'd
Andrew> have to ifdef it. Which makes it an ia64-only problem,
Andrew> which greatly improves your merge chances ;)
For 2.4, I suspect I need to keep this in the ia64 patch anyhow
because it is also necessary to fix scsi_dma.c so it can deal with
allocation bitmaps that are bigger than 32 bits.
I believe ia64 is currently the only platform that supports 64KB
pages. If so, there is probably not much point trying to get this
past Marcelo (and the patch is large enough to have the potential for
introducing new bugs). If another platform cares about this, please
>> - does anyone know of any other code paths where the block size
>> is assumed to fit into 16 bits?
Andrew> Not off the top, but they're probably there.
I'll keep an eye on it. It's working fine so far, but that doesn't
replace a code audit. If you happen to bump into something during
your normal work, please let me know.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/