linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>, linux-mm@kvack.org
Subject: [PATCH v2 0/3] Change calling convention for ->huge_fault
Date: Fri, 18 Aug 2023 21:23:32 +0100	[thread overview]
Message-ID: <20230818202335.2739663-1-willy@infradead.org> (raw)

There are two unrelated changes to the calling convention for
->huge_fault.  I've bundled them together to help people notice the
change.  The first is to improve scalability of DAX page faults by
allowing them to be handled under the VMA lock.  The second is to remove
enum page_entry_size since it's really unnecessary.  The changelogs
and documentation updates hopefully work to that end.

I vaguely contemplated introducing PTE_ORDER to replace use of the bare
'0' order.  I'll happily do it if anyone feels strongly about it.

v2:
 - Split into three patches
 - Use PAGE_SHIFT instead of PTE_SHIFT to fix build errors on hexagon & csky

Matthew Wilcox (Oracle) (3):
  mm: Move PMD_ORDER to pgtable.h
  mm: Allow ->huge_fault() to be called without the mmap_lock held
  mm: Remove enum page_entry_size

 Documentation/filesystems/locking.rst | 36 +++++++++++++++++----------
 Documentation/filesystems/porting.rst | 11 ++++++++
 drivers/dax/device.c                  | 22 ++++++----------
 fs/dax.c                              | 33 ++++++------------------
 fs/erofs/data.c                       |  6 ++---
 fs/ext2/file.c                        |  2 +-
 fs/ext4/file.c                        | 11 ++++----
 fs/fuse/dax.c                         | 20 +++++++--------
 fs/xfs/xfs_file.c                     | 24 +++++++++---------
 fs/xfs/xfs_trace.h                    | 22 ++++++++--------
 include/linux/dax.h                   |  4 +--
 include/linux/mm.h                    | 10 +-------
 include/linux/pgtable.h               |  3 +++
 mm/memory.c                           | 30 +++++-----------------
 14 files changed, 102 insertions(+), 132 deletions(-)

-- 
2.40.1



             reply	other threads:[~2023-08-18 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 20:23 Matthew Wilcox (Oracle) [this message]
2023-08-18 20:23 ` [PATCH v2 1/3] mm: Move PMD_ORDER to pgtable.h Matthew Wilcox (Oracle)
2023-08-18 20:23 ` [PATCH v2 2/3] mm: Allow ->huge_fault() to be called without the mmap_lock held Matthew Wilcox (Oracle)
2023-08-18 20:23 ` [PATCH v2 3/3] mm: Remove enum page_entry_size Matthew Wilcox (Oracle)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230818202335.2739663-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox