From: Steven Rostedt <rostedt@goodmis.org>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Daniel Wagner <dwagner@suse.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Hillf Danton <hdanton@sina.com>, Michal Hocko <mhocko@suse.com>,
Matthew Wilcox <willy@infradead.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>
Subject: Re: [PATCH 1/1] mm/vmalloc: remove preempt_disable/enable when do preloading
Date: Wed, 9 Oct 2019 14:21:25 -0400 [thread overview]
Message-ID: <20191009142125.22cf3b8c@gandalf.local.home> (raw)
In-Reply-To: <20191009164934.10166-1-urezki@gmail.com>
On Wed, 9 Oct 2019 18:49:34 +0200
"Uladzislau Rezki (Sony)" <urezki@gmail.com> wrote:
> Get rid of preempt_disable() and preempt_enable() when the
> preload is done for splitting purpose. The reason is that
> calling spin_lock() with disabled preemtion is forbidden in
> CONFIG_PREEMPT_RT kernel.
>
> Therefore, we do not guarantee that a CPU is preloaded, instead
> we minimize the case when it is not with this change.
>
> For example i run the special test case that follows the preload
> pattern and path. 20 "unbind" threads run it and each does
> 1000000 allocations. Only 3.5 times among 1000000 a CPU was
> not preloaded thus. So it can happen but the number is rather
> negligible.
Thanks for the analysis.
>
> Fixes: 82dd23e84be3 ("mm/vmalloc.c: preload a CPU with one object for split purpose")
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> ---
> mm/vmalloc.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index e92ff5f7dd8b..2ed6fef86950 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -1078,9 +1078,12 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
>
> retry:
> /*
> - * Preload this CPU with one extra vmap_area object to ensure
> - * that we have it available when fit type of free area is
> - * NE_FIT_TYPE.
> + * Preload this CPU with one extra vmap_area object. It is used
> + * when fit type of free area is NE_FIT_TYPE. Please note, it
> + * does not guarantee that an allocation occurs on a CPU that
> + * is preloaded, instead we minimize the case when it is not.
> + * It can happen because of migration, because there is a race
> + * until the below spinlock is taken.
> *
> * The preload is done in non-atomic context, thus it allows us
> * to use more permissive allocation masks to be more stable under
> @@ -1089,20 +1092,16 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
> * Even if it fails we do not really care about that. Just proceed
> * as it is. "overflow" path will refill the cache we allocate from.
> */
> - preempt_disable();
> - if (!__this_cpu_read(ne_fit_preload_node)) {
> - preempt_enable();
As the original code enables preemption here regardless, there's no
guarantee that the original patch would allocate the pva to the CPU in
question.
I agree with this patch, the preempt_disable() here only narrows an
already narrow window, with no real help in what it was doing.
> + if (!this_cpu_read(ne_fit_preload_node)) {
> pva = kmem_cache_alloc_node(vmap_area_cachep, GFP_KERNEL, node);
If the memory allocation failed here, we still may not have a pva for
the current CPU's ne_fit_preload_node, rare as that may be.
> - preempt_disable();
>
> - if (__this_cpu_cmpxchg(ne_fit_preload_node, NULL, pva)) {
> + if (this_cpu_cmpxchg(ne_fit_preload_node, NULL, pva)) {
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
> if (pva)
> kmem_cache_free(vmap_area_cachep, pva);
> }
> }
>
> spin_lock(&vmap_area_lock);
> - preempt_enable();
>
> /*
> * If an allocation fails, the "vend" address is
next prev parent reply other threads:[~2019-10-09 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 16:49 [PATCH 1/1] mm/vmalloc: remove preempt_disable/enable when do preloading Uladzislau Rezki (Sony)
2019-10-09 18:21 ` Steven Rostedt [this message]
2019-10-09 22:19 ` Andrew Morton
2019-10-10 2:17 ` Steven Rostedt
2019-10-10 15:17 ` Uladzislau Rezki
2019-10-11 23:55 ` Andrew Morton
2019-10-14 14:27 ` Uladzislau Rezki
2019-10-14 16:30 ` Michal Hocko
2019-10-15 9:54 ` Uladzislau Rezki
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=20191009142125.22cf3b8c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=dwagner@suse.de \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).