From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Daniel Wagner <dwagner@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: vmalloc: Use the vmap_area_lock to protect ne_fit_preload_node
Date: Fri, 4 Oct 2019 19:45:53 +0200 [thread overview]
Message-ID: <20191004174553.5fk2amnp4jblc7cy@linutronix.de> (raw)
In-Reply-To: <20191004170411.GA31114@pc636>
On 2019-10-04 19:04:11 [+0200], Uladzislau Rezki wrote:
> if another, we can free the object allocated on previous step if
> it already has it. If another CPU does not have it, save it in
> ne_fit_preload_node for another current CPU to reuse later. Further
> we can not migrate because of:
>
> <snip>
> spin_lock(&vmap_area_lock);
> preempt_enable();
> <snip>
ah right. So you keep the lock later on, I somehow missed that part.
That way it actually makes sense.
Sebastian
next prev parent reply other threads:[~2019-10-04 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 9:09 [PATCH] mm: vmalloc: Use the vmap_area_lock to protect ne_fit_preload_node Daniel Wagner
2019-10-03 11:55 ` Uladzislau Rezki
2019-10-04 15:37 ` Sebastian Andrzej Siewior
2019-10-04 16:20 ` Uladzislau Rezki
2019-10-04 16:30 ` Sebastian Andrzej Siewior
2019-10-04 17:04 ` Uladzislau Rezki
2019-10-04 17:45 ` Sebastian Andrzej Siewior [this message]
2019-10-07 8:30 ` Daniel Wagner
2019-10-07 10:56 ` Sebastian Andrzej Siewior
2019-10-07 16:23 ` Uladzislau Rezki
2019-10-07 16:34 ` Daniel Wagner
2019-10-07 16:56 ` Uladzislau Rezki
2019-10-07 17:22 ` Daniel Wagner
2019-10-07 17:36 ` Sebastian Andrzej Siewior
2019-10-07 21:44 ` Uladzislau Rezki
2019-10-08 16:04 ` Uladzislau Rezki
2019-10-09 6:05 ` Daniel Wagner
2019-10-09 9:47 ` Uladzislau Rezki
2019-10-07 8:27 ` Daniel Wagner
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=20191004174553.5fk2amnp4jblc7cy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dwagner@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=urezki@gmail.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 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.