From: Dennis Zhou <dennis@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
tj@kernel.org, hughd@google.com, vbabka@suse.cz,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v4] percpu_counter: add a cmpxchg-based _add_batch variant
Date: Tue, 28 May 2024 16:24:37 -0700 [thread overview]
Message-ID: <ZlZntVycT45knbwB@snowbird> (raw)
In-Reply-To: <20240528141929.ba7e59e4cae89eec01631306@linux-foundation.org>
Hi Andrew,
On Tue, May 28, 2024 at 02:19:29PM -0700, Andrew Morton wrote:
> On Tue, 28 May 2024 13:56:58 -0700 Dennis Zhou <dennis@kernel.org> wrote:
>
> > > EXPORT_SYMBOL(percpu_counter_add_batch);
> > >
> > > /*
> > > --
> > > 2.39.2
> > >
> >
> > Andrew you picked up the __this_cpu_try_cmpxchg() patches. At this point
> > you might as well pick up this too. The cpumask clean ups are likely
> > going to give me trouble later this week when I rebase so I'll probably
> > have to base my percpuh hotplug branch on your mm-unstable now.
>
> Well, if it makes more sense to carry these in a different tree, let's
> do that.
Regarding percpu, I've generally care for that allocator and to varying
degrees corresponding libraries for the last 6 years. I usually take
them in [1] if I have other stuff to run.
The cpumask stuff should not roll up through me, and I think likely you.
It's just a little unfortunate in timing as I was planning on respinning
the percpu hotplug stuff this week (not 100% sure anything will conflict
yet til I do it).
Thanks,
Dennis
[1] https://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git
prev parent reply other threads:[~2024-05-28 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 20:42 [PATCH v4] percpu_counter: add a cmpxchg-based _add_batch variant Mateusz Guzik
2024-05-28 20:56 ` Dennis Zhou
2024-05-28 21:19 ` Andrew Morton
2024-05-28 23:24 ` Dennis Zhou [this message]
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=ZlZntVycT45knbwB@snowbird \
--to=dennis@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjguzik@gmail.com \
--cc=tj@kernel.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.