[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230327102845.GB7701@hirez.programming.kicks-ass.net>
Date: Mon, 27 Mar 2023 12:28:45 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Bernd Schubert <bschubert@....com>
Cc: Ingo Molnar <mingo@...hat.com>, Miklos Szeredi <miklos@...redi.hu>,
Dharmendra Singh <dsingh@....com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Amir Goldstein <amir73il@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: fuse uring / wake_up on the same core
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?
Powered by blists - more mailing lists