From: Andi Kleen <ak@suse.de>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andi Kleen <ak@suse.de>, Brent Casavant <bcasavan@sgi.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Wed, 15 Dec 2004 08:46:36 +0100 [thread overview]
Message-ID: <20041215074636.GR27225@wotan.suse.de> (raw)
In-Reply-To: <41BFEAA5.1090109@cosmosbay.com>
On Wed, Dec 15, 2004 at 08:41:25AM +0100, Eric Dumazet wrote:
>
> My questions are :
>
> 1) Are the route cache and tcp hashes use big pages (2MB) on 2.6.5/2.6.9
> x86_64 kernels.
Yes.
On i386 kernels you can use mem=nopentium to force 4K pages for
the direct mapping, but that was dropped on x86-64.
> 2) What are the exact number of data TLB entries (for small pages and
> huge ones) for opterons ?
check the data sheets, but iirc 64 large DTLBs and 1024+ 4K DTLBS.
That is the L2 TLB, there is also a L1 but it is likely inclusive (?)
> 3) All networks interrupts are handled by CPU0. Should we really use
> NUMA interleaved memory for hashes in this case ?
First it depends on if you run irqbalanced or not and how many
interrupt sources you have.
Even when they are only handled on irq0 it can be still a good idea
to interleave to use the bandwidth of all memory controllers
in the system evenly.
-Andi
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-12-15 7:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 17:53 Brent Casavant
2004-12-14 18:59 ` Martin J. Bligh
2004-12-14 19:13 ` Andi Kleen
2004-12-14 19:48 ` Brent Casavant
2004-12-14 20:08 ` Martin J. Bligh
2004-12-14 23:24 ` Brent Casavant
2004-12-14 22:00 ` Martin J. Bligh
2004-12-15 4:58 ` Andi Kleen
2004-12-15 14:47 ` Anton Blanchard
2004-12-15 23:37 ` Brent Casavant
2004-12-16 5:02 ` Andi Kleen
2004-12-16 5:13 ` Anton Blanchard
2004-12-16 14:18 ` Jose R. Santos
2004-12-20 16:56 ` Jose R. Santos
2004-12-21 11:46 ` Anton Blanchard
2004-12-21 16:23 ` Brent Casavant
2004-12-23 2:19 ` Jose R. Santos
2004-12-15 4:08 ` Andi Kleen
2004-12-15 7:14 ` Martin J. Bligh
2004-12-15 7:17 ` Andi Kleen
2004-12-15 15:08 ` Martin J. Bligh
2004-12-15 18:24 ` Brent Casavant
2004-12-15 7:41 ` Eric Dumazet
2004-12-15 7:46 ` Andi Kleen [this message]
2004-12-15 9:14 ` Andi Kleen
2004-12-14 23:24 ` Nick Piggin
2004-12-14 19:30 ` Brent Casavant
2004-12-14 20:10 ` Martin J. Bligh
2004-12-14 18:32 Luck, Tony
2004-12-15 0:28 ` Hiroyuki KAMEZAWA
2004-12-15 17:25 Luck, Tony
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=20041215074636.GR27225@wotan.suse.de \
--to=ak@suse.de \
--cc=bcasavan@sgi.com \
--cc=dada1@cosmosbay.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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