From: Davide Libenzi <davidel@xmailserver.org>
To: Hubertus Frnake <frankeh@watson.ibm.com>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net, ak@suse.de
Subject: Re: [Lse-tech] Re: CPU affinity & IPI latency (FIX)_
Date: Tue, 17 Jul 2001 11:11:55 -0700 (PDT) [thread overview]
Message-ID: <XFMail.20010717111155.davidel@xmailserver.org> (raw)
In-Reply-To: <3B5476E0.EBC7CA12@watson.ibm.com>
On 17-Jul-2001 Hubertus Frnake wrote:
> In an attempt to inline the code, somehow the tabs got lost. So here is the
> attached correct patch fo 2.4.5. Please try and let me know whether you
> see your problems disappear and/or others arise.
> The sketchy writeup is still the same.
What is the reason You don't set the resched task in the fast path ?
best_cpu = p->processor;
if (can_schedule(p, best_cpu)) {
tsk = idle_task(best_cpu);
if ((cpu_curr(best_cpu) == tsk) &&
(cpu_resched(best_cpu) == NULL)) {
int need_resched;
send_now_idle:
/*
* If need_resched == -1 then we can skip sending
* the IPI altogether, tsk->need_resched is
* actively watched by the idle thread.
*/
need_resched = tsk->need_resched;
tsk->need_resched = 1;
if ((best_cpu != this_cpu) && !need_resched) {
>>>> cpu_resched(best_cpu) = p;
smp_send_reschedule(best_cpu);
}
return;
}
}
- Davide
next prev parent reply other threads:[~2001-07-17 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF46AE0C03.7FA13916-ON85256A8C.005E4CEB@pok.ibm.com>
2001-07-17 17:33 ` [Lse-tech] Re: CPU affinity & IPI latency (FIX)_ Hubertus Frnake
2001-07-17 18:00 ` Davide Libenzi
2001-07-17 18:11 ` Davide Libenzi [this message]
[not found] <OF51487F8A.564A5A7D-ON85256A8C.0063C208@pok.ibm.com>
2001-07-17 18:12 ` Hubertus Franke
2001-07-17 18:28 Hubertus Franke
2001-07-19 16:56 ` Davide Libenzi
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=XFMail.20010717111155.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=ak@suse.de \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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