linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	yangshiguang1011@163.com, akpm@linux-foundation.org,
	cl@gentwo.org, rientjes@google.com, roman.gushchin@linux.dev,
	glittao@gmail.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	yangshiguang <yangshiguang@xiaomi.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] mm: slub: avoid wake up kswapd in set_track_prepare
Date: Wed, 27 Aug 2025 10:44:37 +0200	[thread overview]
Message-ID: <36584aaa-7f9b-407b-ad10-64a6ae619235@suse.cz> (raw)
In-Reply-To: <6be0c134-b5b0-4ff9-9d2a-4b68f22c3762@suse.cz>

On 8/27/25 10:00, Vlastimil Babka wrote:
> On 8/27/25 07:17, Harry Yoo wrote:
>> On Mon, Aug 25, 2025 at 05:42:52PM +0200, Vlastimil Babka wrote:
>>> On 8/25/25 14:40, Matthew Wilcox wrote:
>>> > On Mon, Aug 25, 2025 at 08:17:37PM +0800, yangshiguang1011@163.com wrote:
>>> >> Avoid deadlock caused by implicitly waking up kswapd by
>>> >> passing in allocation flags.
>>> > [...]
>>> >> +	/* Preemption is disabled in ___slab_alloc() */
>>> >> +	gfp_flags &= ~(__GFP_DIRECT_RECLAIM);
>>> > 
>>> > If you don't mean __GFP_KSWAPD_RECLAIM here, the explanation needs to
>>> > be better.
>>> 
>>> It was suggested by Harry here:
>>> https://lore.kernel.org/all/aKKhUoUkRNDkFYYb@harry
>>> 
>>> I think the comment is enough? Disabling preemption means we can't direct
>>> reclaim, but we can wake up kswapd. If the slab caller context is such that
>>> we can't, __GFP_KSWAPD_RECLAIM already won't be in the gfp_flags.
>> 
>> To make it a little bit more verbose, this ^^ explanation can be added to the
>> changelog?
>> 
>>> But I think we should mask our also __GFP_NOFAIL and add __GFP_NOWARN?
>> 
>> That sounds good.
>> 
>>> (we should get some common helpers for these kinds of gfp flag manipulations
>>> already)
>> 
>> Any ideas for its name?
>> 
>> gfp_dont_try_too_hard(),
>> gfp_adjust_lightweight(),
>> gfp_adjust_mayfail(),
>> ...
>> 
>> I'm not good at naming :/
> 
> Looks like there's already gfp_nested_mask() for these purposes. I'm not
> sure if it should be allowing GFP_ATOMIC (thus __GFP_HIGH) as it does
> though. Seems to contradict the comment about not exhausing reserves. Wonder
> if that was raised during review...

Looks like I mentioned it but inconclusively.

https://lore.kernel.org/linux-xfs/1fb5b8f3-d8c7-4350-888a-ad8f4d54bc66@suse.cz/

Anyway that's orthogonal to using the helper here right now.

> The masking out of __GFP_DIRECT_RECLAIM is specific to the slab case so we
> don't need a helper for that (unless we find other users). It could be then
> e.g. gfp_nested_mask_noblock() ?
> 



      reply	other threads:[~2025-08-27  8:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 12:17 yangshiguang1011
2025-08-25 12:40 ` Matthew Wilcox
2025-08-25 15:42   ` Vlastimil Babka
2025-08-27  5:17     ` Harry Yoo
2025-08-27  7:45       ` yangshiguang
2025-08-27  8:40         ` Vlastimil Babka
2025-08-29 11:29           ` yangshiguang
2025-08-29 13:08             ` Vlastimil Babka
2025-08-30  1:48               ` yangshiguang
2025-08-27  8:00       ` Vlastimil Babka
2025-08-27  8:44         ` Vlastimil Babka [this message]

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=36584aaa-7f9b-407b-ad10-64a6ae619235@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=glittao@gmail.com \
    --cc=harry.yoo@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=yangshiguang1011@163.com \
    --cc=yangshiguang@xiaomi.com \
    /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