Hi,
The topic came up in a recent discussion about how to deal with large folios
when it comes to swap as a swap device is normally considered a simple array
of PAGE_SIZE-sized elements that can be indexed by a single integer.
With the advent of large folios, however, we might need to change this in
order to be better able to swap out a compound page efficiently. Swap
fragmentation raises its head, as does the need to potentially save multiple
indices per folio. Does swap need to grow more filesystem features?
Further to this, we have at least two ways to cache data on disk/flash/etc. -
swap and fscache - and both want to set aside disk space for their operation.
Might it be possible to combine the two?
One thing I want to look at for fscache is the possibility of switching from a
file-per-object-based approach to a tagged cache more akin to the way OpenAFS
does things. In OpenAFS, you have a whole bunch of small files, each
containing a single block (e.g. 256K) of data, and an index that maps a
particular {volume,file,version,block} to one of these files in the cache.
Now, I could also consider holding all the data blocks in a single file (or
blockdev) - and this might work for swap. For fscache, I do, however, need to
have some sort of integrity across reboots that swap does not require.
David
