From: Marcelo Tosatti <mtosatti@redhat.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Leonardo Bras <leobras.c@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Waiman Long <longman@redhat.com>,
Boqun Feun <boqun.feng@gmail.com>
Subject: Re: [PATCH v3 0/4] Introduce QPW for per-cpu operations (v3)
Date: Mon, 18 May 2026 13:24:42 -0300 [thread overview]
Message-ID: <ags9StiliW+fB1lV@tpad> (raw)
In-Reply-To: <agsMqeTRU9MbzdQk@localhost.localdomain>
On Mon, May 18, 2026 at 02:57:13PM +0200, Frederic Weisbecker wrote:
> Hi,
>
> Is there any plan to proceed with this patchset?
>
> Thanks.
Yes, will address Sashiko's comments and repost.
next prev parent reply other threads:[~2026-05-22 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 17:55 [PATCH v3 0/4] Introduce QPW for per-cpu operations (v3) Marcelo Tosatti
2026-03-23 17:55 ` [PATCH v3 1/4] Introducing qpw_lock() and per-cpu queue & flush work Marcelo Tosatti
2026-03-24 0:38 ` Leonardo Bras
2026-03-23 17:55 ` [PATCH v3 2/4] mm/swap: move bh draining into a separate workqueue Marcelo Tosatti
2026-03-23 17:55 ` [PATCH v3 3/4] swap: apply new queue_percpu_work_on() interface Marcelo Tosatti
2026-04-01 15:01 ` Frederic Weisbecker
2026-03-23 17:55 ` [PATCH v3 4/4] slub: " Marcelo Tosatti
2026-04-01 15:10 ` Frederic Weisbecker
2026-04-15 21:10 ` [PATCH v3 0/4] Introduce QPW for per-cpu operations (v3) Leonardo Bras
2026-05-18 12:57 ` Frederic Weisbecker
2026-05-18 16:24 ` Marcelo Tosatti [this message]
2026-05-18 23:36 ` Leonardo Bras
2026-05-20 12:06 ` Frederic Weisbecker
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=ags9StiliW+fB1lV@tpad \
--to=mtosatti@redhat.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=cl@linux.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tglx@linutronix.de \
--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.