diff options
| author | NeilBrown <[email protected]> | 2022-05-09 18:20:47 -0700 |
|---|---|---|
| committer | akpm <[email protected]> | 2022-05-09 18:20:47 -0700 |
| commit | 4c4a763406ef903b78334bd2ccea168d2f7a741a (patch) | |
| tree | 9dff8e975ae6375ccbc82d72b028d523eadefffa /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 014bb1de4fc17d54907d54418126a9a9736f4aff (diff) | |
mm: drop swap_dirty_folio
folios that are written to swap are owned by the MM subsystem - not any
filesystem.
When such a folio is passed to a filesystem to be written out to a
swap-file, the filesystem handles the data, but the folio itself does not
belong to the filesystem. So calling the filesystem's ->dirty_folio()
address_space operation makes no sense. This is for folios in the given
address space, and a folio to be written to swap does not exist in the
given address space.
So drop swap_dirty_folio() which calls the address-space's
->dirty_folio(), and always use noop_dirty_folio(), which is appropriate
for folios being swapped out.
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: NeilBrown <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Tested-by: David Howells <[email protected]>
Tested-by: Geert Uytterhoeven <[email protected]>
Cc: Hugh Dickins <[email protected]>
Cc: Mel Gorman <[email protected]>
Cc: Trond Myklebust <[email protected]>
Cc: Miaohe Lin <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions