linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Mike.stroya@hp.com, GOTO <y-goto@jp.fujitsu.com>,
	dmosberger@gmail.com, hugh@veritas.com
Subject: Re: [BUGFIX][PATCH] DO flush icache before set_pte() on ia64.
Date: Fri, 6 Jul 2007 10:32:29 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707061032040.30575@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070705125427.9a3b8e8b.kamezawa.hiroyu@jp.fujitsu.com>

I am a bit worried about the performance impact of all this flushing? What 
is the worst case scenario here?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2007-07-06 17:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  6:05 KAMEZAWA Hiroyuki
2007-07-04  6:31 ` Nick Piggin
2007-07-04  7:38   ` KAMEZAWA Hiroyuki
2007-07-05  2:04     ` Nick Piggin
2007-07-05  2:47       ` KAMEZAWA Hiroyuki
2007-07-05  3:19         ` Nick Piggin
2007-07-05  3:54           ` KAMEZAWA Hiroyuki
2007-07-05  4:29             ` Nick Piggin
2007-07-06 17:32             ` Christoph Lameter [this message]
2007-07-06 21:57               ` KAMEZAWA Hiroyuki
2007-07-05 18:13 ` Mike Stroyan
2007-07-05 22:18   ` KAMEZAWA Hiroyuki
2007-07-06  0:20     ` KAMEZAWA Hiroyuki
2007-07-05 22:27   ` KAMEZAWA Hiroyuki

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=Pine.LNX.4.64.0707061032040.30575@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=Mike.stroya@hp.com \
    --cc=dmosberger@gmail.com \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tony.luck@intel.com \
    --cc=y-goto@jp.fujitsu.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