linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Pekka Enberg <penberg@gmail.com>, Muchun Song <songmuchun@bytedance.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] mm/page_alloc: skip setting nodemask when we are in interrupt
Date: Fri, 3 Jul 2020 09:20:27 +0200	[thread overview]
Message-ID: <fe891223-9f83-d112-b185-643d6121712d@redhat.com> (raw)
In-Reply-To: <CAOJsxLGc-o1Os7HAoQmhd1DNxGWVrfbw2R8NroTQg0wHNyWX1w@mail.gmail.com>

On 03.07.20 08:34, Pekka Enberg wrote:
> On Fri, Jul 3, 2020 at 9:14 AM Muchun Song <songmuchun@bytedance.com> wrote:
>>
>> When we are in the interrupt context, it is irrelevant to the
>> current task context. If we use current task's mems_allowed, we
>> can fair to alloc pages in the fast path and fall back to slow
>> path memory allocation when the current node(which is the current
>> task mems_allowed) does not have enough memory to allocate. In
>> this case, it slows down the memory allocation speed of interrupt
>> context. So we can skip setting the nodemask to allow any node
>> to allocate memory, so that fast path allocation can success.
>>
>> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
>> ---
>>  mm/page_alloc.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index b48336e20bdcd..a6c36cd557d1d 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -4726,10 +4726,12 @@ static inline bool prepare_alloc_pages(gfp_t gfp_mask, unsigned int order,
>>
>>         if (cpusets_enabled()) {
>>                 *alloc_mask |= __GFP_HARDWALL;
>> -               if (!ac->nodemask)
>> -                       ac->nodemask = &cpuset_current_mems_allowed;
>> -               else
>> +               if (!ac->nodemask) {
>> +                       if (!in_interrupt())
>> +                               ac->nodemask = &cpuset_current_mems_allowed;
> 
> If !ac->nodemask and in_interrupt() the ALLOC_CPUSET flag is not set,
> which by-passes the __cpuset_zone_allowed() check for allocations.
> This works fine because in the case if in_interrupt() the function
> allows allocation on any zone/node.
> 
>> +               } else {
>>                         *alloc_flags |= ALLOC_CPUSET;
>> +               }
>>         }
> 
> However, if you write the condition as follows:
> 
>         if (cpusets_enabled()) {
>                 *alloc_mask |= __GFP_HARDWALL;
>                 if (!in_interrupt() && !ac->nodemask)
>                         ac->nodemask = &cpuset_current_mems_allowed;
>                 else
>                         *alloc_flags |= ALLOC_CPUSET;
>         }

^ looks much cleaner as well. Do we want to add a summarizing comment?

> 
> then the code is future-proof in case of __cpuset_zone_allowed() is
> one day extended to support IRQ context too (it probably should
> eventually respect IRQ SMP affinity).



-- 
Thanks,

David / dhildenb



  reply	other threads:[~2020-07-03  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03  6:13 Muchun Song
2020-07-03  6:34 ` Pekka Enberg
2020-07-03  7:20   ` David Hildenbrand [this message]
2020-07-03  7:47     ` Pekka Enberg

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=fe891223-9f83-d112-b185-643d6121712d@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@gmail.com \
    --cc=songmuchun@bytedance.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