From: Bernd Schubert <bschubert@ddn.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Cc: Joanne Koong <joannelkoong@gmail.com>,
Luis Henriques <luis@igalia.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fuse: Wake requests on the same cpu
Date: Tue, 14 Oct 2025 09:12:17 +0000 [thread overview]
Message-ID: <9a39bba7-1ffb-4dd5-adb5-bf7516578288@ddn.com> (raw)
In-Reply-To: <f2906e44-413f-4153-a378-5a87a49298d4@wdc.com>
On 10/14/25 09:25, Johannes Thumshirn wrote:
> [You don't often get email from johannes.thumshirn@wdc.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On 10/13/25 9:01 PM, Bernd Schubert wrote:
>> +/**
>> + * __wake_up - wake up threads blocked on a waitqueue, on the current cpu
> That needs to be __wake_up_on_current_cpu
> [..]
>> void __wake_up_on_current_cpu(struct wait_queue_head *wq_head, unsigned int mode, void *key)
>> {
>> __wake_up_common_lock(wq_head, mode, 1, WF_CURRENT_CPU, key);
>> }
>> +EXPORT_SYMBOL_GPL(__wake_up_on_current_cpu);
>
>
Oops, thanks and spotting! v2 is coming.
Thanks,
Bernd
prev parent reply other threads:[~2025-10-14 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 17:27 [PATCH] fuse: Wake requests on the same cpu Bernd Schubert
2025-10-14 7:25 ` Johannes Thumshirn
2025-10-14 9:12 ` Bernd Schubert [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=9a39bba7-1ffb-4dd5-adb5-bf7516578288@ddn.com \
--to=bschubert@ddn.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joannelkoong@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=mgorman@suse.de \
--cc=miklos@szeredi.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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).