From: Hillf Danton <hdanton@sina.com>
To: Bernd Schubert <bschubert@ddn.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Miklos Szeredi <miklos@szeredi.hu>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Andrei Vagin <avagin@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: fuse uring / wake_up on the same core
Date: Sat, 29 Apr 2023 07:37:59 +0800 [thread overview]
Message-ID: <20230428233759.2677-1-hdanton@sina.com> (raw)
In-Reply-To: <d954ca54-2a3f-b111-7ba5-41169de473ce@ddn.com>
On 28 Apr 2023 21:54:51 +0000 Bernd Schubert <bschubert@ddn.com>
> > @@ -7424,6 +7424,8 @@ select_task_rq_fair(struct task_struct *
> > if (wake_flags & WF_TTWU) {
> > record_wakee(p);
> >
> > + if (p->seesaw && current->seesaw)
> > + return cpu;
> > if (sched_energy_enabled()) {
> > new_cpu = find_energy_efficient_cpu(p, prev_cpu);
> > if (new_cpu >= 0)
>
> Hmm, WF_CURRENT_CPU works rather similar, except that it tests if cpu is
> in cpus_ptr? The combination of both patches results in
I missed checking cpu against p. Good catch.
next prev parent reply other threads:[~2023-04-28 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d0ed1dbd-1b7e-bf98-65c0-7f61dd1a3228@ddn.com>
[not found] ` <20230327102845.GB7701@hirez.programming.kicks-ass.net>
[not found] ` <20230427122417.2452-1-hdanton@sina.com>
[not found] ` <3c0facd0-e3c7-0aa1-8b2e-961120d4f43d@ddn.com>
2023-04-28 1:44 ` Hillf Danton
2023-04-28 21:54 ` Bernd Schubert
2023-04-28 23:37 ` Hillf Danton [this message]
2023-05-01 21:44 ` Bernd Schubert
[not found] ` <20230502003335.3253-1-hdanton@sina.com>
2023-05-03 17:04 ` Bernd Schubert
2023-05-04 2:16 ` Hillf Danton
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=20230428233759.2677-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=avagin@gmail.com \
--cc=bschubert@ddn.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--cc=peterz@infradead.org \
/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