From: Matthew Wilcox <willy@infradead.org>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
RCU <rcu@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>
Subject: Re: [PATCH 1/1] rcu/tree: add emergency pool for headless case
Date: Fri, 3 Apr 2020 11:16:55 -0700 [thread overview]
Message-ID: <20200403181655.GR21484@bombadil.infradead.org> (raw)
In-Reply-To: <20200403173051.4081-1-urezki@gmail.com>
On Fri, Apr 03, 2020 at 07:30:51PM +0200, Uladzislau Rezki (Sony) wrote:
> @@ -2877,6 +2885,12 @@ struct kfree_rcu_cpu {
> bool initialized;
> // Number of objects for which GP not started
> int count;
> +
> + /*
> + * Reserved emergency pool for headless variant.
> + */
> + int nr_emergency;
> + void **emergency;
This is a pretty expensive way to maintain an emergency pool.
Try something like this ...
struct emergency_pool_object {
union {
struct whatever foo;
struct {
int remaining;
void *next;
};
};
};
struct kfree_rcu_cpu {
...
struct emergency_pool_object *epo;
};
struct whatever *get_emergency_object(struct kfree_rcu_cpu *krc)
{
struct emergency_pool_object *epo = krc->epo;
if (epo)
krc->epo = epo->next;
return &epo->foo;
}
void alloc_emergency_objects(struct kfree_rcu_cpu *krc, int n)
{
int i = 0;
if (krc->epo)
i = krc->epo->remaining;
while (++i < n) {
struct emergency_pool_object *epo = kmalloc(sizeof(epo), GFP);
epo->remaining = i;
epo->next = krc->epo;
krc->epo = epo;
}
}
next prev parent reply other threads:[~2020-04-03 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 17:30 Uladzislau Rezki (Sony)
2020-04-03 18:16 ` Matthew Wilcox [this message]
2020-04-04 19:09 ` Uladzislau Rezki
2020-04-03 19:14 ` Paul E. McKenney
2020-04-04 19:10 ` Uladzislau Rezki
2020-04-04 19:51 ` Joel Fernandes
2020-04-05 17:21 ` Uladzislau Rezki
2020-04-05 23:30 ` Joel Fernandes
2020-04-06 12:56 ` Uladzislau Rezki
2020-04-06 15:18 ` Joel Fernandes
2020-04-06 16:17 ` Uladzislau Rezki
2020-04-07 1:47 ` Joel Fernandes
2020-04-06 15:31 ` Paul E. McKenney
2020-04-06 16:32 ` 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=20200403181655.GR21484@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox