On Mon, Mar 22, 2021 at 06:47:44PM +0000, Matthew Wilcox wrote: > On Mon, Mar 22, 2021 at 01:59:24PM -0400, Johannes Weiner wrote: > > On Sat, Mar 20, 2021 at 05:40:37AM +0000, Matthew Wilcox (Oracle) wrote: > > > This series introduces the 'struct folio' as a replacement for > > > head-or-base pages. This initial set reduces the kernel size by > > > approximately 6kB, although its real purpose is adding infrastructure > > > to enable further use of the folio. > > > > > > The intent is to convert all filesystems and some device drivers to work > > > in terms of folios. This series contains a lot of explicit conversions, > > > but it's important to realise it's removing a lot of implicit conversions > > > in some relatively hot paths. There will be very few conversions from > > > folios when this work is completed; filesystems, the page cache, the > > > LRU and so on will generally only deal with folios. > > > > If that is the case, shouldn't there in the long term only be very > > few, easy to review instances of things like compound_head(), > > PAGE_SIZE etc. deep in the heart of MM? And everybody else should 1) > > never see tail pages and 2) never assume a compile-time page size? > > I don't know exactly where we get to eventually. There are definitely > some aspects of the filesystem<->mm interface which are page-based > (eg ->fault needs to look up the exact page, regardless of its > head/tail/base nature), while ->readpage needs to talk in terms of > folios. I can imagine we'd eventually want fault handlers that can also fill in larger chunks of data if the file is of the right size and the MM is able to (and policy/heuristics determine to) go with a huge page. > > What are the higher-level places that in the long-term should be > > dealing with tail pages at all? Are there legit ones besides the page > > allocator, THP splitting internals & pte-mapped compound pages? > > I can't tell. I think this patch maybe illustrates some of the > problems, but maybe it's just an intermediate problem: > > https://git.infradead.org/users/willy/pagecache.git/commitdiff/047e9185dc146b18f56c6df0b49fe798f1805c7b > > It deals mostly in terms of folios, but when it needs to kmap() and > memcmp(), then it needs to work in terms of pages. I don't think it's > avoidable (maybe we bury the "dealing with pages" inside a kmap() > wrapper somewhere, but I'm not sure that's better). Yeah it'd be nice to get low-level, PAGE_SIZE pages out of there. We may be able to just kmap whole folios too, which are more likely to be small pages on highmem systems anyway. > > Some compound_head() that are currently in the codebase are already > > unnecessary. Like the one in activate_page(). > > Right! And it's hard to find & remove them without very careful analysis, > or particularly deep knowledge. With folios, we can remove them without > terribly deep thought. True. It definitely also helps mark the places that have been converted from the top down and which ones haven't. Without that you need to think harder about the context ("How would a tail page even get here?" vs. "No page can get here, only folios" ;-)) Again, I think that's something that would automatically be better in the long term when compound_page() and PAGE_SIZE themselves would stand out like sore thumbs. But you raise a good point: there is such an overwhelming amount of them right now that it's difficult to do this without a clearer marker and help from the type system. > > And looking at grep, I wouldn't be surprised if only the page table > > walkers need the page_compound() that mark_page_accessed() does. We > > would be better off if they did the translation once and explicitly in > > the outer scope, where it's clear they're dealing with a pte-mapped > > compound page, instead of having a series of rather low level helpers > > (page flags testing, refcount operations, LRU operations, stat > > accounting) all trying to be clever but really just obscuring things > > and imposing unnecessary costs on the vast majority of cases. > > > > So I fully agree with the motivation behind this patch. But I do > > wonder why it's special-casing the commmon case instead of the rare > > case. It comes at a huge cost. Short term, the churn of replacing > > 'page' with 'folio' in pretty much all instances is enormous. > > Because people (think they) know what a page is. It's PAGE_SIZE bytes > long, it occupies one PTE, etc, etc. A folio is new and instead of > changing how something familiar (a page) behaves, we're asking them > to think about something new instead that behaves a lot like a page, > but has differences. Yeah, that makes sense. > > And longer term, I'm not convinced folio is the abstraction we want > > throughout the kernel. If nobody should be dealing with tail pages in > > the first place, why are we making everybody think in 'folios'? Why > > does a filesystem care that huge pages are composed of multiple base > > pages internally? This feels like an implementation detail leaking out > > of the MM code. The vast majority of places should be thinking 'page' > > with a size of 'page_size()'. Including most parts of the MM itself. > > I think pages already leaked out of the MM and into filesystems (and > most of the filesystem writers seem pretty unknowledgable about how > pages and the page cache work, TBH). That's OK! Or it should be OK. > Filesystem authors should be experts on how their filesystem works. > Everywhere that they have to learn about the page cache is a distraction > and annoyance for them. > > I mean, I already tried what you're suggesting. It's really freaking > hard. It's hard to do, it's hard to explain, it's hard to know if you > got it right. With folios, I've got the compiler working for me, telling > me that I got some of the low-level bits right (or wrong), leaving me > free to notice "Oh, wait, we got the accounting wrong because writeback > assumes that a page is only PAGE_SIZE bytes". I would _never_ have > noticed that with the THP tree. I only noticed it because transitioning > things to folios made me read the writeback code and wonder about the > 'inc_wb_stat' call, see that it's measuring something in 'number of pages' > and realise that the wb_stat accounting needs to be fixed. I agree with all of this whole-heartedly. The reason I asked about who would deal with tail pages in the long term is because I think optimally most places would just think of these things as descriptors for variable lengths of memory. And only the allocator looks behind the curtain and deals with the (current!) reality that they're stitched together from fixed-size objects. To me, folios seem to further highlight this implementation detail, more so than saying a page is now page_size() - although I readily accept that the latter didn't turn out to be a viable mid-term strategy in practice at all, and that a clean break is necessary sooner rather than later (instead of cleaning up the page api now and replacing the backing pages with struct hwpage or something later). The name of the abstraction indicates how we think we're supposed to use it, what behavior stands out as undesirable. For example, you brought up kmap/memcpy/usercopy, which is a pretty common operation. Should they continue to deal with individual tail pages, and thereby perpetuate the exposure of these low-level MM building blocks to drivers and filesystems? It means portfolio -> page lookups will remain common - and certainly the concept of the folio suggests thinking of it as a couple of pages strung together. And the more this is the case, the less it stands out when somebody is dealing with low-level pages when really they shouldn't be - the thing this is trying to fix. Granted it's narrowing the channel quite a bit. But it's also so pervasively used that I do wonder if it's possible to keep up with creative new abuses. But I also worry about the longevity of the concept in general. This is one of the most central and fundamental concepts in the kernel. Is this going to make sense in the future? In 5 years even? > > The compile-time check is nice, but I'm not sure it would be that much > > more effective at catching things than a few centrally placed warns > > inside PageFoo(), get_page() etc. and other things that should not > > encounter tail pages in the first place (with __helpers for the few > > instances that do). And given the invasiveness of this change, they > > ought to be very drastically better at it, and obviously so, IMO. > > We should have come up with a new type 15 years ago instead of doing THP. > But the second best time to invent a new type for "memory objects which > are at least as big as a page" is right now. Because it only gets more > painful over time. Yes and no. Yes because I fully agree that too much detail of the pages have leaked into all kinds of places where they shouldn't be, and a new abstraction for what most places interact with is a good idea IMO. But we're also headed in a direction with the VM that give me pause about the folios-are-multiple-pages abstraction. How long are we going to have multiple pages behind a huge page? Common storage drives are getting fast enough that simple buffered IO workloads are becoming limited by CPU, just because it's too many individual pages to push through the cache. We have pending patches to rewrite the reclaim algorithm because rmap is falling apart with the rate of paging we're doing. We'll need larger pages in the VM not just for optimizing TLB access, but to cut transaction overhead for paging in general (I know you're already onboard with this, especially on the page cache side, just stating it for completeness). But for that to work, we'll need the allocator to produce huge pages at the necessary rate, too. The current implementation likely won't scale. Compaction is expensive enough that we have to weigh when to allocate huge pages for long-lived anon regions, let alone allocate them for streaming IO cache entries. But if the overwhelming number of requests going to the page allocator are larger than 4k pages - anon regions? check. page cache? likely a sizable share. slub? check. network? check - does it even make sense to have that as the default block size for the page allocator anymore? Or even allocate struct page at this granularity? So I think transitioning away from ye olde page is a great idea. I wonder this: have we mapped out the near future of the VM enough to say that the folio is the right abstraction? What does 'folio' mean when it corresponds to either a single page or some slab-type object with no dedicated page? If we go through with all the churn now anyway, IMO it makes at least sense to ditch all association and conceptual proximity to the hardware page or collections thereof. Simply say it's some length of memory, and keep thing-to-page translations out of the public API from the start. I mean, is there a good reason to keep this baggage? mem_t or something. mem = find_get_mem(mapping, offset); p = kmap(mem, offset - mem_file_offset(mem), len); copy_from_user(p, buf, len); kunmap(mem); SetMemDirty(mem); put_mem(mem); There are 10k instances of 'page' in mm/ outside the page allocator, a majority of which will be the new thing. 14k in fs. I don't think I have the strength to type shrink_folio_list(), or explain to new people what it means, years after it has stopped making sense.
