linux.git/mm/page-writeback.c, branch v6.5

writeback: account the number of pages written back

2023-07-08T16:29:30+00:00

nr_to_write is a count of pages, so we need to decrease it by the number
of pages in the folio we just wrote, not by 1.  Most callers specify
either LONG_MAX or 1, so are unaffected, but writeback_sb_inodes() might
end up writing 512x as many pages as it asked for.

Dave added:

: XFS is the only filesystem this would affect, right?  AFAIA, nothing
: else enables large folios and uses writeback through
: write_cache_pages() at this point...
: 
: In which case, I'd be surprised if much difference, if any, gets
: noticed by anyone.

Link: https://lkml.kernel.org/r/20230628185548.981888-1-willy@infradead.org
Fixes: 793917d997df ("mm/readahead: Add large folio readahead")
Signed-off-by: Matthew Wilcox (Oracle) 
Reviewed-by: Christoph Hellwig 
Cc: Jan Kara 
Cc: Dave Chinner 
Signed-off-by: Andrew Morton

mm: kill lock|unlock_page_memcg()

2023-06-19T23:19:33+00:00

Since commit c7c3dec1c9db ("mm: rmap: remove lock_page_memcg()"),
no more user, kill lock_page_memcg() and unlock_page_memcg().

Link: https://lkml.kernel.org/r/20230614143612.62575-1-wangkefeng.wang@huawei.com
Signed-off-by: Kefeng Wang 
Acked-by: Johannes Weiner 
Reviewed-by: Matthew Wilcox (Oracle) 
Signed-off-by: Andrew Morton

mm,jfs: move write_one_page/folio_write_one to jfs

2023-03-13T00:00:42+00:00

The last remaining user of folio_write_one through the write_one_page
wrapper is jfs, so move the functionality there and hard code the
call to metapage_writepage.

Note that the use of the pagecache by the JFS 'metapage' buffer cache
is a bit odd, and we could probably do without VM-level dirty tracking
at all, but that's a change for another time.

Signed-off-by: Christoph Hellwig 
Acked-by: Dave Kleikamp 
Signed-off-by: Al Viro

fs: convert writepage_t callback to pass a folio

2023-02-03T06:33:34+00:00

Patch series "Convert writepage_t to use a folio".

More folioisation.  I split out the mpage work from everything else
because it completely dominated the patch, but some implementations I just
converted outright.


This patch (of 2):

We always write back an entire folio, but that's currently passed as the
head page.  Convert all filesystems that use write_cache_pages() to expect
a folio instead of a page.

Link: https://lkml.kernel.org/r/20230126201255.1681189-1-willy@infradead.org
Link: https://lkml.kernel.org/r/20230126201255.1681189-2-willy@infradead.org
Signed-off-by: Matthew Wilcox (Oracle) 
Cc: Christoph Hellwig 
Signed-off-by: Andrew Morton

mm/fs: convert inode_attach_wb() to take a folio

2023-02-03T06:33:19+00:00

Patch series "Writeback folio conversions".

Remove more calls to compound_head() by passing folios around instead of
pages.


This patch (of 2):

The only caller of inode_attach_wb() which doesn't pass NULL already has a
folio, so convert the whole call-chain to take folios.

Link: https://lkml.kernel.org/r/20230116192507.2146150-1-willy@infradead.org
Link: https://lkml.kernel.org/r/20230116192507.2146150-2-willy@infradead.org
Signed-off-by: Matthew Wilcox (Oracle) 
Signed-off-by: Andrew Morton

page-writeback: convert write_cache_pages() to use filemap_get_folios_tag()

2023-02-03T06:33:14+00:00

Convert function to use folios throughout.  This is in preparation for the
removal of find_get_pages_range_tag().  This change removes 8 calls to
compound_head(), and the function now supports large folios.

Link: https://lkml.kernel.org/r/20230104211448.4804-5-vishal.moola@gmail.com
Signed-off-by: Vishal Moola (Oracle) 
Reviewed-by: Matthew Wilcow (Oracle) 
Signed-off-by: Andrew Morton

mm: remove zap_page_range and create zap_vma_pages

2023-01-19T01:12:55+00:00

zap_page_range was originally designed to unmap pages within an address
range that could span multiple vmas.  While working on [1], it was
discovered that all callers of zap_page_range pass a range entirely within
a single vma.  In addition, the mmu notification call within zap_page
range does not correctly handle ranges that span multiple vmas.  When
crossing a vma boundary, a new mmu_notifier_range_init/end call pair with
the new vma should be made.

Instead of fixing zap_page_range, do the following:
- Create a new routine zap_vma_pages() that will remove all pages within
  the passed vma.  Most users of zap_page_range pass the entire vma and
  can use this new routine.
- For callers of zap_page_range not passing the entire vma, instead call
  zap_page_range_single().
- Remove zap_page_range.

[1] https://lore.kernel.org/linux-mm/20221114235507.294320-2-mike.kravetz@oracle.com/
Link: https://lkml.kernel.org/r/20230104002732.232573-1-mike.kravetz@oracle.com
Signed-off-by: Mike Kravetz 
Suggested-by: Peter Xu 
Acked-by: Michal Hocko 
Acked-by: Peter Xu 
Acked-by: Heiko Carstens 	[s390]
Reviewed-by: Christoph Hellwig 
Cc: Christian Borntraeger 
Cc: Christian Brauner 
Cc: Dave Hansen 
Cc: David Hildenbrand 
Cc: Eric Dumazet 
Cc: Matthew Wilcox 
Cc: Michael Ellerman 
Cc: Nadav Amit 
Cc: Palmer Dabbelt 
Cc: Rik van Riel 
Cc: Vlastimil Babka 
Cc: Will Deacon 
Signed-off-by: Andrew Morton

mm: remove generic_writepages

2023-01-19T01:12:51+00:00

Now that all external callers are gone, just fold it into do_writepages.

Link: https://lkml.kernel.org/r/20221229161031.391878-7-hch@lst.de
Signed-off-by: Christoph Hellwig 
Reviewed-by: Jan Kara 
Cc: Joel Becker 
Cc: Joseph Qi 
Cc: Konstantin Komarov 
Cc: Mark Fasheh 
Cc: Matthew Wilcox 
Cc: Theodore Ts'o 
Signed-off-by: Andrew Morton

mm/swap: convert deactivate_page() to folio_deactivate()

2023-01-19T01:12:47+00:00

Deactivate_page() has already been converted to use folios, this change
converts it to take in a folio argument instead of calling page_folio(). 
It also renames the function folio_deactivate() to be more consistent with
other folio functions.

[akpm@linux-foundation.org: fix left-over comments, per Yu Zhao]
Link: https://lkml.kernel.org/r/20221221180848.20774-5-vishal.moola@gmail.com
Signed-off-by: Vishal Moola (Oracle) 
Reviewed-by: Matthew Wilcox (Oracle) 
Reviewed-by: SeongJae Park 
Signed-off-by: Andrew Morton

mm: add bdi_set_min_ratio_no_scale() function

2022-11-30T23:59:06+00:00

This introduces bdi_set_min_ratio_no_scale(). It uses the max
granularity for the ratio. This function by the new sysfs knob
min_ratio_fine.

Link: https://lkml.kernel.org/r/20221119005215.3052436-19-shr@devkernel.io
Signed-off-by: Stefan Roesch 
Cc: Chris Mason 
Cc: Jens Axboe 
Signed-off-by: Andrew Morton