Garrett D'Amore wrote: > Darren J Moffat wrote: >> With the updated name I have only one possible small issue. >> >> You said the driver is hardcoded to 512 byte blocks, yet the industry >> is moving towards 4k blocks. Is that likely to be an issue for >> devices driven by 'blkdev' ? > > I don't think so. If the application (or other code) issues smaller > I/Os, the underlying driver will have to implement as RMW. If the > filesystem or app code uses 4K aligned and sized buffers, then there > won't be a need to do RMW.
I understood how that side would work. > We might need to change the code slightly to express the 4K size in the > various ioctls, but that can happen latter when I run into such a > device. (The current devices supported by this device driver all use > 512 byte blocks.) My concern is when there are devices that use 4K size blocks instead of 512 byte blocks. Is there anything in the architecture of bd that means they can't easily be supported by this bd driver ? -- Darren J Moffat
