linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>, Andi Kleen <ak@suse.de>,
	Brent Casavant <bcasavan@sgi.com>
Cc: 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 09:25:55 -0800	[thread overview]
Message-ID: <B8E391BBE9FE384DAA4C5C003888BE6F02900608@scsmsx401.amr.corp.intel.com> (raw)

>> Also at least on IA64 the large page size is usually 1-2GB 
>> and that would seem to be a little too large to me for
>> interleaving purposes. Also it may prevent the purpose 
>> you implemented it - not using too much memory from a single
>> node. 
>
>Yes, that'd bork it. But I thought that they had a large sheaf of
>mapping sizes to chose from on ia64?

Yes, ia64 supports lots of pagesizes (the exact list for each cpu
model can be found in /proc/pal/cpu*/vm_info, but the architecture
requires that 4k, 8k, 16k, 64k, 256k, 1m, 4m, 16m, 64m, 256m be
supported by all implementations).  To make good use of them
for vmalloc() would require that we switch the kernel over to
using long format VHPT ... as well as all the architecture
independent changes that Andi listed.

It would be interesting to see some perfmon data on TLB miss rates
before and after this patch, but I'd personally be amazed if you
could find a macro-level benchmark that could reliably detect the
perfomance effects relating to TLB caused by this change.

-Tony
--
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>

             reply	other threads:[~2004-12-15 17:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 17:25 Luck, Tony [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-14 18:32 Luck, Tony
2004-12-15  0:28 ` Hiroyuki KAMEZAWA
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
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

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=B8E391BBE9FE384DAA4C5C003888BE6F02900608@scsmsx401.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=ak@suse.de \
    --cc=bcasavan@sgi.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