From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-arch@vger.kernel.org, steiner@sgi.com,
mort@wildopensource.com, jbarnes@sgi.com
Subject: Re: Fw: Re: Reduce TLB flushing during process migration
Date: Wed, 12 May 2004 16:57:06 -0700 [thread overview]
Message-ID: <20040512165706.14d3b0ea.davem@redhat.com> (raw)
In-Reply-To: <20040512153203.5ac1b196.akpm@osdl.org>
On Wed, 12 May 2004 15:32:03 -0700
Andrew Morton <akpm@osdl.org> wrote:
> davem, you expressed interest in this previously. The question is whether
> we should remove the whole thing, or just the ia64 component?
It doesn't do anything for me on sparc64. As per the change
description, it's a benefit also on platforms like x86 where
context-switch == tlb flush anyways.
At least that was my understanding.
If it's beneficial to the ia64 folks, I'm ambivalent, so just
put the fixed version back in once available.
next prev parent reply other threads:[~2004-05-12 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:32 Fw: Re: Reduce TLB flushing during process migration Andrew Morton
2004-05-12 23:57 ` David S. Miller [this message]
2004-05-13 7:43 ` Andi Kleen
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=20040512165706.14d3b0ea.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@osdl.org \
--cc=jbarnes@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=mort@wildopensource.com \
--cc=steiner@sgi.com \
/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