Date: Thu, 10 Aug 2000 18:06:38 +0200
From: Roman Zippel <[EMAIL PROTECTED]>
I have a suggestion for 2.5 (and an almost working patch): isn't it
about time to introduce a bdev_t structure that contains all the
information that is scattered over lots of places?
That would be:
struct block_device
struct gendisk
struct sec_size
struct blk_dev_struct
read_ahead
blk_dev_struct
blk_size
blksize_size
hardsect_size
max_readahead
max_sectors
max_segments
ro_bits
Yes, something like this has been discussed before. It's probably a
good idea for 2.5. It's not strictly speaking a fs issue, though. It's
much more of a device-driver API issue.
- Ted
