public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Mosberger-Tang" <dmosberger@gmail.com>
To: Zoltan Menyhart <Zoltan.Menyhart@bull.net>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org, Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito
Date: Wed, 01 Aug 2007 13:44:31 +0000	[thread overview]
Message-ID: <ed5aea430708010644t5eb961f3nb133354ee5cb071a@mail.gmail.com> (raw)
In-Reply-To: <46B0549A.1010308@bull.net>

On 8/1/07, Zoltan Menyhart <Zoltan.Menyhart@bull.net> wrote:

> You do have model specific I cache semantics.
> Not taking it into account will oblige you to flush in vain for the models
> which do not require it. Why do you want to take this option?

Given unlimited resources, your proposal makes perfect sense.  We
could have a Linux version for Merced, one for McKinley, one for
Madison, etc., etc.

(Un)fortunately, resources are limited and with that constraint in
place, rather than spending lots of time optimizing the kernel for
particular idiosyncrasies of a CPU model, it is generally much better
to optimize it for the things the hardware designers promised us would
stay the same across CPU models (i.e., the "architecture").  Sure, it
may mean that on occasion certain things are slightly slower than they
could be but it does have the decided advantage of letting the
maintainers sleep at night... ;-)  Moreover, higher-level
optimizations usually have much higher payoff, so even though you may
do things a bit more slowly at the lowest level, you may end up with a
faster system overall because you were able to spend more time
optimizing at a higher level.

  --david

      reply	other threads:[~2007-08-01 13:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31  2:35 [PATCH] flush icache before set_pte take6. [0/4] KAMEZAWA Hiroyuki
2007-07-31  2:38 ` [PATCH] flush icache before set_pte take6. [1/4] migration fix KAMEZAWA Hiroyuki
2007-07-31  2:39 ` [PATCH] flush icache before set_pte take6. [2/4] sync icache dcache KAMEZAWA Hiroyuki
2007-07-31  2:40 ` [PATCH] flush icache before set_pte take6. [3/4] add montecito KAMEZAWA Hiroyuki
2007-07-31  2:41 ` [PATCH] flush icache before set_pte take6. [4/4] optimization for KAMEZAWA Hiroyuki
2007-07-31  4:15   ` [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito David Mosberger-Tang
2007-07-31  4:29     ` [PATCH] flush icache before set_pte take6. [4/4] optimization KAMEZAWA Hiroyuki
2007-07-31  5:02       ` KAMEZAWA Hiroyuki
2007-07-31 17:06       ` [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito Jim Hull
2007-08-01  9:27         ` [PATCH] flush icache before set_pte take6. [4/4] optimization Zoltan Menyhart
2007-07-31  8:38     ` Zoltan Menyhart
2007-07-31 10:17       ` KAMEZAWA Hiroyuki
2007-07-31 11:02         ` Zoltan Menyhart
2007-07-31 16:39 ` [PATCH] flush icache before set_pte take6. [3/4] add montecito brand name Luck, Tony
2007-08-01  0:17   ` [PATCH] flush icache before set_pte take6. [3/4] add montecito KAMEZAWA Hiroyuki
2007-07-31 16:44 ` [PATCH] flush icache before set_pte take6. [4/4] optimization for cpus other than montecito Luck, Tony
2007-08-01  9:38   ` [PATCH] flush icache before set_pte take6. [4/4] optimization Zoltan Menyhart
2007-08-01 13:44     ` David Mosberger-Tang [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=ed5aea430708010644t5eb961f3nb133354ee5cb071a@mail.gmail.com \
    --to=dmosberger@gmail.com \
    --cc=Zoltan.Menyhart@bull.net \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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