[lkml]   [2019]   [Nov]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectHow to avoid using bmap in cachefiles -- FS-Cache/CacheFiles rewrite
Hi Christoph,

I've been rewriting cachefiles in the kernel and it now uses kiocbs to do
async direct I/O to/from the cache files - which seems to make a 40-48% speed

However, I've replaced the use of bmap internally to detect whether data is
present or not - which is dodgy for a number of reasons, not least that
extent-based filesystems might insert or remove blocks of zeros to shape the
extents better, thereby rendering the metadata information useless for

But using a separate map has a couple of problems:

(1) The map is metadata kept outside of the filesystem journal, so coherency
management is necessary

(2) The map gets hard to manage for very large files (I'm using 256KiB
granules, so 1 bit per granule means a 512-byte map block can span 1GiB)
and xattrs can be of limited capacity.

I seem to remember you said something along the lines of it being possible to
tell the filesystem not to do discarding and insertion of blocks of zeros. Is
there a generic way to do that?

Also, is it possible to make it so that I can tell an O_DIRECT read to fail
partially or, better, completely if there's no data to be had in part of the
range? I can see DIO_SKIP_HOLES, but that only seems to affect writes


 \ /
  Last update: 2019-11-14 14:41    [W:0.072 / U:0.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site