From: Vlastimil Babka <vbabka@suse.cz>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
"Paul E . McKenney" <paulmck@kernel.org>
Cc: RCU <rcu@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Frederic Weisbecker <frederic@kernel.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH 1/4] rcu/kvfree: Support dynamic rcu_head for single argument objects
Date: Wed, 28 Aug 2024 16:58:48 +0200 [thread overview]
Message-ID: <64bebc29-a007-4ebc-bf86-8c2c0a7e6bf6@suse.cz> (raw)
In-Reply-To: <20240828110929.3713-1-urezki@gmail.com>
On 8/28/24 13:09, Uladzislau Rezki (Sony) wrote:
> Add a support of dynamically attaching an rcu_head to an object
> which gets freed via the single argument of kvfree_rcu(). This is
> used in the path, when a page allocation fails due to a high memory
> pressure.
>
> The basic idea behind of this is to minimize a hit of slow path
> which requires a caller to wait until a grace period is passed.
>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
So IIUC it's a situation where we can't allocate a page, but we hope the
kmalloc-32 slab has still free objects to give us dyn_rcu_head's before it
would have to also make a page allocation?
So that may really be possible and there might potentially be many such
objects, but I wonder if there's really a benefit. The system is struggling
for memory and the single-argument caller specifically is _mightsleep so it
could e.g. instead go direct reclaim a page rather than start depleting the
kmalloc-32 slab, no?
> ---
> kernel/rcu/tree.c | 53 +++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 49 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index be00aac5f4e7..0124411fecfb 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -3425,6 +3425,11 @@ kvfree_rcu_bulk(struct kfree_rcu_cpu *krcp,
> cond_resched_tasks_rcu_qs();
> }
>
> +struct dyn_rcu_head {
> + unsigned long *ptr;
> + struct rcu_head rh;
> +};
> +
> static void
> kvfree_rcu_list(struct rcu_head *head)
> {
> @@ -3433,15 +3438,32 @@ kvfree_rcu_list(struct rcu_head *head)
> for (; head; head = next) {
> void *ptr = (void *) head->func;
> unsigned long offset = (void *) head - ptr;
> + struct dyn_rcu_head *drhp = NULL;
> +
> + /*
> + * For dynamically attached rcu_head, a ->func field
> + * points to _offset_, i.e. not to a pointer which has
> + * to be freed. For such objects, adjust an offset and
> + * pointer.
> + */
> + if (__is_kvfree_rcu_offset((unsigned long) ptr)) {
> + drhp = container_of(head, struct dyn_rcu_head, rh);
> + offset = (unsigned long) drhp->rh.func;
> + ptr = drhp->ptr;
> + }
>
> next = head->next;
> debug_rcu_head_unqueue((struct rcu_head *)ptr);
> rcu_lock_acquire(&rcu_callback_map);
> trace_rcu_invoke_kvfree_callback(rcu_state.name, head, offset);
>
> - if (!WARN_ON_ONCE(!__is_kvfree_rcu_offset(offset)))
> + if (!WARN_ON_ONCE(!__is_kvfree_rcu_offset(offset))) {
> kvfree(ptr);
>
> + if (drhp)
> + kvfree(drhp);
> + }
> +
> rcu_lock_release(&rcu_callback_map);
> cond_resched_tasks_rcu_qs();
> }
> @@ -3787,6 +3809,21 @@ add_ptr_to_bulk_krc_lock(struct kfree_rcu_cpu **krcp,
> return true;
> }
>
> +static struct rcu_head *
> +attach_rcu_head_to_object(void *obj)
> +{
> + struct dyn_rcu_head *rhp;
> +
> + rhp = kmalloc(sizeof(struct dyn_rcu_head), GFP_KERNEL |
> + __GFP_NORETRY | __GFP_NOMEMALLOC | __GFP_NOWARN);
> +
> + if (!rhp)
> + return NULL;
> +
> + rhp->ptr = obj;
> + return &rhp->rh;
> +}
> +
> /*
> * Queue a request for lazy invocation of the appropriate free routine
> * after a grace period. Please note that three paths are maintained,
> @@ -3830,9 +3867,17 @@ void kvfree_call_rcu(struct rcu_head *head, void *ptr)
> if (!success) {
> run_page_cache_worker(krcp);
>
> - if (head == NULL)
> - // Inline if kvfree_rcu(one_arg) call.
> - goto unlock_return;
> + if (!head) {
> + krc_this_cpu_unlock(krcp, flags);
> + head = attach_rcu_head_to_object(ptr);
> + krcp = krc_this_cpu_lock(&flags);
> +
> + if (!head)
> + // Inline if kvfree_rcu(one_arg) call.
> + goto unlock_return;
> +
> + ptr = (rcu_callback_t) offsetof(struct dyn_rcu_head, rh);
> + }
>
> head->func = ptr;
> head->next = krcp->head;
next prev parent reply other threads:[~2024-08-28 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 11:09 [PATCH 1/4] rcu/kvfree: Support dynamic rcu_head for single argument objects Uladzislau Rezki (Sony)
2024-08-28 11:09 ` [PATCH 2/4] rcu/kvfree: Add a switcher for dynamic rcu_head Uladzislau Rezki (Sony)
2024-08-28 11:09 ` [PATCH 3/4] rcu/kvfree: Use polled API in a slow path Uladzislau Rezki (Sony)
2024-08-28 11:09 ` [PATCH 4/4] rcu/kvfree: Switch to expedited version in " Uladzislau Rezki (Sony)
2024-08-28 14:58 ` Vlastimil Babka [this message]
2024-08-28 17:00 ` [PATCH 1/4] rcu/kvfree: Support dynamic rcu_head for single argument objects Uladzislau Rezki
2024-08-28 18:00 ` Paul E. McKenney
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=64bebc29-a007-4ebc-bf86-8c2c0a7e6bf6@suse.cz \
--to=vbabka@suse.cz \
--cc=Neeraj.Upadhyay@amd.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=rcu@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 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).