From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: O(1) MQ scheduler J9 patch for IA64
Date: Fri, 08 Feb 2002 06:40:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698806027@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698806025@msgid-missing>
>>>>> On Thu, 7 Feb 2002 22:37:41 -0800, William Lee Irwin III <wli@holomorphy.com> said:
Bill> On Thu, Feb 07, 2002 at 10:11:28PM -0800, David Mosberger
Bill> wrote:
>> A somewhat cheesy solution might be to have a per-CPU flag that
>> indicates whether a CPU should flush its TLB before switching to
>> the next task. We could check for this in activate_mm(). Do you
>> want to try this?
Bill> Would this be a good thing to put in the mmu_context? It seems
Bill> like that could isolate it within arch-specific code.
It's arch-specific either way. The flag needs to be per CPU, not per task.
--david
next prev parent reply other threads:[~2002-02-08 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 6:11 [Linux-ia64] Re: O(1) MQ scheduler J9 patch for IA64 David Mosberger
2002-02-08 6:37 ` William Lee Irwin III
2002-02-08 6:40 ` David Mosberger [this message]
2002-02-08 17:37 ` [Linux-ia64] Re: O(1) MQ scheduler J9 patch for IA64 -> K3 patch Erich Focht
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-105590698806027@msgid-missing \
--to=davidm@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