From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-mm@kvack.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>
Subject: [PATCH 0/3] few mm helpers for bcachefs
Date: Tue, 6 Feb 2024 16:50:13 -0500 [thread overview]
Message-ID: <20240206215016.961253-1-kent.overstreet@linux.dev> (raw)
memalloc_flags_{save,restore} - cleanup of the existing duplication in
our memalloc_*_{save,restore} functions
PF_MEMALLOC_NORECLAIM, PF_MEMALLOC_NOWARN: we've been talking about
getting away from gfp flags for years, but we've been lacking some
PF_MEMALLOC_* equivalents that we need to make that happen - this adds
some of the missing ones.
they're needed for calling alloc_inode() in bcachefs with btree locks
held (so that we can make lookup() properly transactional), since it
doesn't take a gfp flags param and adding it would require changing
methods in every fs.
Kent Overstreet (3):
mm: introduce memalloc_flags_{save,restore}
mm: introduce PF_MEMALLOC_NORECLAIM, PF_MEMALLOC_NOWARN
mempool: kvmalloc pool
include/linux/mempool.h | 13 +++++++++
include/linux/sched.h | 4 +--
include/linux/sched/mm.h | 60 ++++++++++++++++++++++++++--------------
mm/mempool.c | 13 +++++++++
4 files changed, 67 insertions(+), 23 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-06 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 21:50 Kent Overstreet [this message]
2024-02-06 21:50 ` [PATCH 1/3] mm: introduce memalloc_flags_{save,restore} Kent Overstreet
2024-02-09 10:36 ` Vlastimil Babka
2024-02-06 21:50 ` [PATCH 2/3] mm: introduce PF_MEMALLOC_NORECLAIM, PF_MEMALLOC_NOWARN Kent Overstreet
2024-02-07 7:24 ` Vlastimil Babka
2024-02-07 7:44 ` Michal Hocko
2024-02-07 21:05 ` Kent Overstreet
2024-02-06 21:50 ` [PATCH 3/3] mempool: kvmalloc pool Kent Overstreet
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=20240206215016.961253-1-kent.overstreet@linux.dev \
--to=kent.overstreet@linux.dev \
--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