Re: mm: don't read i_size of inode unless we need it

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Btw, given that you're micro-optimizing in this area:

block devices still use ->direct_IO in the I/O path.  It might make
sense to switch to the model of the file systems that use iomap where
we avoid that indirect call and can optimize the code for the direct
I/O fast path.  With that you woudn't even end up using this i_size_read
at all




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux