diff options
| author | Tal Zussman <tz2294@columbia.edu> | 2026-08-09 16:07:10 -0400 |
|---|---|---|
| committer | Mike Marshall <hubcap@omnibond.com> | 2026-08-11 14:03:11 -0400 |
| commit | 5f13fae5580a835d1d9fb22f9b87b4affb2db846 (patch) | |
| tree | e49a4984d6931e56c641d2abe42468284d979c46 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | f574296be7f46eb60beca851240b526df232f480 (diff) | |
orangefs: use folio_pos() and folio_size() in orangefs_page_mkwrite()
orangefs_page_mkwrite() records the faulted range with
page_offset(vmf->page) and PAGE_SIZE, although the write range it sets
is attached to the folio and the rest of the function already operates
on folios. Use folio_pos() and folio_size() instead. This gets rid of
two calls to page_offset(), removing two calls to compound_head().
No functional change. orangefs folios are always order-0, so the values
are identical. However, if orangefs ever enables large folios, this
change is necessary for correctness with the current write range
tracking scheme. Tracking only a single page of a larger folio would
leave the rest of the folio's dirty data outside the range that gets
written back, leading to data loss.
Signed-off-by: Tal Zussman <tz2294@columbia.edu>
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions
