All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Uladzislau Rezki <urezki@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	David Rientjes <rientjes@google.com>,
	Christoph Lameter <cl@linux.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	Christian Brauner <brauner@kernel.org>, RCU <rcu@vger.kernel.org>,
	Shakeel Butt <shakeel.butt@linux.dev>
Subject: Re: [GIT PULL] slab updates for 6.11
Date: Thu, 26 Sep 2024 19:07:03 +0200	[thread overview]
Message-ID: <ZvWUt2oyXRsvJRNc@pc636> (raw)
In-Reply-To: <88ed491f-4ae4-4cfc-9be2-dda3de56813c@suse.cz>

On Thu, Sep 26, 2024 at 06:46:29PM +0200, Vlastimil Babka wrote:
> On 9/26/24 18:40, Uladzislau Rezki wrote:
> > On Thu, Sep 26, 2024 at 06:35:27PM +0200, Vlastimil Babka wrote:
> >> On 9/18/24 16:40, Uladzislau Rezki wrote:
> >> >>
> >> > Thank you for valuable feedback! Indeed it is hard to follow, even
> >> > though it works correctly.
> >> > I will add the comment and also break the loop on first queuing as you
> >> > suggested!
> >> > 
> >> > It does not make sense to loop further because following iterations
> >> > are never successful
> >> > thus never overwrite "queued" variable(it never reaches the
> >> > queue_rcu_work() call).
> >> > 
> >> > <snip>
> >> >          bool queued = false;
> >> >          ...
> >> >          for (i = 0; i < KFREE_N_BATCHES; i++) {
> >> >                 if (need_offload_krc(krcp)) {
> >> >                          queued = queue_rcu_work(system_wq, &krwp->rcu_work);
> >> >          ...
> >> >          return queued;
> >> > <snip>
> >> > 
> >> > if we queued, "if(need_offload_krc())" condition is never true anymore.
> >> > 
> >> > Below refactoring makes it clear. I will send the patch to address it.
> >> 
> >> Looks good, AFAICT. Can you send the full patch then? Thanks.
> >> 
> > I will do so. We can send it from RCU-side for rcX, this merge window or
> > you can do it.
> > 
> > What is the best for you?
> 
> Guess I could do via slab tree since the original commit went there too.
> 
Make sense. I will send to you then!

--
Uladzislau Rezki

  reply	other threads:[~2024-09-26 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  9:45 [GIT PULL] slab updates for 6.11 Vlastimil Babka
2024-09-18  7:06 ` Linus Torvalds
2024-09-18 14:40   ` Uladzislau Rezki
2024-09-26 16:35     ` Vlastimil Babka
2024-09-26 16:40       ` Uladzislau Rezki
2024-09-26 16:46         ` Vlastimil Babka
2024-09-26 17:07           ` Uladzislau Rezki [this message]
2024-09-18  8:10 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-07-17 10:49 Vlastimil Babka
2024-07-18 23:06 ` pr-tracker-bot

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=ZvWUt2oyXRsvJRNc@pc636 \
    --to=urezki@gmail.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rcu@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    /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.