From: Andi Kleen <ak@suse.de>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, piggin@cyberone.com.au,
mjbligh@us.ibm.com, ricklind@us.ibm.com, akpm@osdl.org
Subject: Re: 2.6.5-rc3-mm4 x86_64 sched domains patch
Date: Wed, 14 Apr 2004 15:44:56 +0200 [thread overview]
Message-ID: <20040414154456.78893f3f.ak@suse.de> (raw)
In-Reply-To: <1081466480.10774.0.camel@farah>
On Thu, 08 Apr 2004 16:22:09 -0700
Darren Hart <dvhltc@us.ibm.com> wrote:
>
> This patch is intended as a quick fix for the x86_64 problem, and
Ingo's latest tweaks seemed to already cure STREAM, but some more
tuning is probably a good idea agreed.
> doesn't solve the problem of how to build generic sched domain
> topologies. We can certainly conceive of various topologies for x86
> systems, so even arch specific topologies may not be sufficient. Would
> sub-arch (ie NUMAQ) be the right way to handle different topologies, or
> will we be able to autodiscover the appropriate topology? I will be
> looking into this more, but thought some might benefit from an immediate
> x86_64 fix. I am very interested in hearing your ideas on this.
The patch doesn't apply against 2.6.5-mm5 anymore. Can you generate a new patch?
I will test it then.
Also it will need merging with the patch that adds SMT support for IA32e machines
on x86-64.
-Andi
next prev parent reply other threads:[~2004-04-14 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 23:22 2.6.5-rc3-mm4 x86_64 sched domains patch Darren Hart
2004-04-08 23:42 ` Nick Piggin
2004-04-11 8:57 ` shai
2004-04-11 9:57 ` Rick Lindsley
2004-04-11 15:07 ` Martin J. Bligh
2004-04-14 13:44 ` Andi Kleen [this message]
2004-04-14 14:14 ` Nick Piggin
2004-04-14 14:41 ` Andi Kleen
2004-04-15 5:51 ` Nick Piggin
2004-04-14 17:24 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2004-04-14 23:20 Siddha, Suresh B
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=20040414154456.78893f3f.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=piggin@cyberone.com.au \
--cc=ricklind@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.