From: Michal Hocko <mhocko@suse.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@techsingularity.net>,
Uladzislau Rezki <urezki@gmail.com>,
Vasily Averin <vvs@virtuozzo.com>, Roman Gushchin <guro@fb.com>,
Andrew Morton <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: page_alloc: skip bulk allocator for __GFP_ACCOUNT
Date: Thu, 14 Oct 2021 09:16:04 +0200 [thread overview]
Message-ID: <YWfZNF7T7Fm69sik@dhcp22.suse.cz> (raw)
In-Reply-To: <20211013194338.1804247-1-shakeelb@google.com>
On Wed 13-10-21 12:43:38, Shakeel Butt wrote:
[...]
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 668edb16446a..b3acad4615d3 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5215,6 +5215,10 @@ unsigned long __alloc_pages_bulk(gfp_t gfp, int preferred_nid,
> unsigned int alloc_flags = ALLOC_WMARK_LOW;
> int nr_populated = 0, nr_account = 0;
>
> + /* Bulk allocator does not support memcg accounting. */
> + if (unlikely(gfp & __GFP_ACCOUNT))
> + goto out;
Did you mean goto failed here? This would break some which do not
have any fallback. E.g. xfs_buf_alloc_pages but likely more.
Sorry I could have been more specific when talking about bypassing the
bulk allocator. It is quite confusing because the bulk allocator
interface consists of the bulk allocator and the fallback to the normal
page allocator.
> +
> /*
> * Skip populated array elements to determine if any pages need
> * to be allocated before disabling IRQs.
> --
> 2.33.0.882.g93a45727a2-goog
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-10-14 7:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 19:43 Shakeel Butt
2021-10-13 22:03 ` Roman Gushchin
2021-10-13 22:26 ` Shakeel Butt
2021-10-13 23:15 ` Roman Gushchin
2021-10-13 23:45 ` Shakeel Butt
2021-10-14 0:06 ` Roman Gushchin
2021-10-14 0:08 ` Matthew Wilcox
2021-10-14 7:05 ` Vasily Averin
2021-10-14 7:18 ` Michal Hocko
2021-10-14 7:16 ` Michal Hocko [this message]
2021-10-14 15:01 ` Shakeel Butt
2021-10-14 15:13 ` Michal Hocko
2021-10-14 15:23 ` Johannes Weiner
2021-10-14 17:43 ` Vasily Averin
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=YWfZNF7T7Fm69sik@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=shakeelb@google.com \
--cc=urezki@gmail.com \
--cc=vvs@virtuozzo.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