From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: switch_mm race condition with Ingo's scheduler
Date: Fri, 12 Jul 2002 18:47:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905774@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805973@msgid-missing>
>>>>> On Fri, 12 Jul 2002 11:02:25 -0700, Grant Grundler <grundler@cup.hp.com> said:
Grant> Would "lazy TLB flushing" be possible?
Grant> ie flush TLB of given taskid first time task needs to run on a CPU.
Grant> Deal with the TLB flushing when running the task,
Grant> not when creating or rescheduling to a different CPU.
There is no good way to distinguish between "running a task for the
first time on a CPU" and "rescheduling". It could be done, but I
don't think it's worth the complexity. The overhead of checking for a
delayed flush is just one load from a CPU-local variable and a test.
That's in the noise compared to a context-switch.
Grant> I'm thinking broadcasting TLB flushes (or IPI for that
Grant> effect) is, uhm, less than optimal for scalability. But I'm
Grant> no expert on CPU TLB issues. There might be lots of evils
Grant> with this approach. I need to read the section on process
Grant> creation/scheduling in the IA64 Linux book. (ie you don't
Grant> need to explain what the book already says).
With Erich's patch, there are no IPIs on wrap-around. That was the
whole point of the patch (to avoid deadlock conditions).
--david
prev parent reply other threads:[~2002-07-12 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 10:45 [Linux-ia64] Re: switch_mm race condition with Ingo's scheduler Erich Focht
2002-07-11 21:50 ` David Mosberger
2002-07-12 16:47 ` Erich Focht
2002-07-12 17:02 ` David Mosberger
2002-07-12 17:26 ` Erich Focht
2002-07-12 17:37 ` David Mosberger
2002-07-12 18:02 ` Grant Grundler
2002-07-12 18:47 ` David Mosberger [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=marc-linux-ia64-105590701905774@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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