From: Peter Zijlstra <peterz@infradead.org>
To: Bernd Schubert <bschubert@ddn.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Dharmendra Singh <dsingh@ddn.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: fuse uring / wake_up on the same core
Date: Mon, 27 Mar 2023 12:28:45 +0200 [thread overview]
Message-ID: <20230327102845.GB7701@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <d0ed1dbd-1b7e-bf98-65c0-7f61dd1a3228@ddn.com>
On Fri, Mar 24, 2023 at 07:50:12PM +0000, Bernd Schubert wrote:
> With the fuse-uring patches that part is basically solved - the waitq
> that that thread is about is not used anymore. But as per above,
> remaining is the waitq of the incoming workq (not mentioned in the
> thread above). As I wrote, I have tried
> __wake_up_sync((x), TASK_NORMAL), but it does not make a difference for
> me - similar to Miklos' testing before. I have also tried struct
> completion / swait - does not make a difference either.
> I can see task_struct has wake_cpu, but there doesn't seem to be a good
> interface to set it.
>
> Any ideas?
Does the stuff from:
https://lkml.kernel.org/r/20230308073201.3102738-1-avagin@google.com
work for you?
next prev parent reply other threads:[~2023-03-27 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 19:50 Bernd Schubert
2023-03-24 22:44 ` Bernd Schubert
[not found] ` <20230325002815.1703-1-hdanton@sina.com>
2023-03-25 7:08 ` K Prateek Nayak
2023-03-27 14:35 ` Bernd Schubert
2023-03-27 10:28 ` Peter Zijlstra [this message]
2023-04-26 22:40 ` Bernd Schubert
[not found] ` <20230427122417.2452-1-hdanton@sina.com>
2023-04-27 13:35 ` Bernd Schubert
[not found] ` <20230428014443.2539-1-hdanton@sina.com>
2023-04-28 21:54 ` Bernd Schubert
2023-05-01 21:44 ` Bernd Schubert
[not found] ` <20230502003335.3253-1-hdanton@sina.com>
2023-05-03 17:04 ` Bernd Schubert
[not found] ` <20230504021656.3823-1-hdanton@sina.com>
2023-05-05 13:10 ` Bernd Schubert
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=20230327102845.GB7701@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=amir73il@gmail.com \
--cc=bschubert@ddn.com \
--cc=dsingh@ddn.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mingo@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
all inboxes | Powered by JetHome®