From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,rppt@kernel.org,pasha.tatashin@soleen.com,mhocko@suse.com,mgorman@techsingularity.net,kent.overstreet@linux.dev,vbabka@suse.cz,akpm@linux-foundation.org
Subject: [folded-merged] mm-document-memalloc_noreclaim_save-and-memalloc_pin_save-v2.patch removed from -mm tree
Date: Wed, 21 Feb 2024 15:50:19 -0800 [thread overview]
Message-ID: <20240221235020.2FF1EC43390@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-document-memalloc_noreclaim_save-and-memalloc_pin_save-v2
has been removed from the -mm tree. Its filename was
mm-document-memalloc_noreclaim_save-and-memalloc_pin_save-v2.patch
This patch was dropped because it was folded into mm-document-memalloc_noreclaim_save-and-memalloc_pin_save.patch
------------------------------------------------------
From: Vlastimil Babka <vbabka@suse.cz>
Subject: mm-document-memalloc_noreclaim_save-and-memalloc_pin_save-v2
Date: Thu, 15 Feb 2024 10:58:28 +0100
fix issues that Mike pointed out
Link: https://lkml.kernel.org/r/20240215095827.13756-2-vbabka@suse.cz
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: Mike Rapoport (IBM) <rppt@kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Mel Gorman <mgorman@techsingularity.net>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/sched/mm.h | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
--- a/include/linux/sched/mm.h~mm-document-memalloc_noreclaim_save-and-memalloc_pin_save-v2
+++ a/include/linux/sched/mm.h
@@ -315,7 +315,8 @@ static inline void might_alloc(gfp_t gfp
* point of view. Use memalloc_noio_restore to end the scope with flags
* returned by this function.
*
- * This function is safe to be used from any context.
+ * Context: This function is safe to be used from any context.
+ * Return: The saved flags to be passed to memalloc_noio_restore.
*/
static inline unsigned int memalloc_noio_save(void)
{
@@ -346,7 +347,8 @@ static inline void memalloc_noio_restore
* point of view. Use memalloc_nofs_restore to end the scope with flags
* returned by this function.
*
- * This function is safe to be used from any context.
+ * Context: This function is safe to be used from any context.
+ * Return: The saved flags to be passed to memalloc_nofs_restore.
*/
static inline unsigned int memalloc_nofs_save(void)
{
@@ -371,7 +373,7 @@ static inline void memalloc_nofs_restore
/**
* memalloc_noreclaim_save - Marks implicit __GFP_MEMALLOC scope.
*
- * This functions marks the beginning of the __GFP_MEMALLOC allocation scope.
+ * This function marks the beginning of the __GFP_MEMALLOC allocation scope.
* All further allocations will implicitly add the __GFP_MEMALLOC flag, which
* prevents entering reclaim and allows access to all memory reserves. This
* should only be used when the caller guarantees the allocation will allow more
@@ -386,8 +388,10 @@ static inline void memalloc_nofs_restore
*
* Individual allocations under the scope can opt out using __GFP_NOMEMALLOC
*
- * This function should not be used in an interrupt context as that one does not
- * give PF_MEMALLOC access to reserves, see __gfp_pfmemalloc_flags().
+ * Context: This function should not be used in an interrupt context as that one
+ * does not give PF_MEMALLOC access to reserves.
+ * See __gfp_pfmemalloc_flags().
+ * Return: The saved flags to be passed to memalloc_noreclaim_restore.
*/
static inline unsigned int memalloc_noreclaim_save(void)
{
@@ -412,10 +416,12 @@ static inline void memalloc_noreclaim_re
/**
* memalloc_pin_save - Marks implicit ~__GFP_MOVABLE scope.
*
- * This functions marks the beginning of the ~__GFP_MOVABLE allocation scope.
+ * This function marks the beginning of the ~__GFP_MOVABLE allocation scope.
* All further allocations will implicitly remove the __GFP_MOVABLE flag, which
* will constraint the allocations to zones that allow long term pinning, i.e.
* not ZONE_MOVABLE zones.
+ *
+ * Return: The saved flags to be passed to memalloc_pin_restore.
*/
static inline unsigned int memalloc_pin_save(void)
{
_
Patches currently in -mm which might be from vbabka@suse.cz are
mm-vmscan-prevent-infinite-loop-for-costly-gfp_noio-__gfp_retry_mayfail-allocations.patch
mm-document-memalloc_noreclaim_save-and-memalloc_pin_save.patch
reply other threads:[~2024-02-21 23:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240221235020.2FF1EC43390@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.