From: Brent Casavant <bcasavan@sgi.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-ia64@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Tue, 14 Dec 2004 13:30:20 -0600 [thread overview]
Message-ID: <Pine.SGI.4.61.0412141319100.22462@kzerza.americas.sgi.com> (raw)
In-Reply-To: <9250000.1103050790@flay>
On Tue, 14 Dec 2004, Martin J. Bligh wrote:
> Yup, makes a lot of sense to me to stripe these, for the caches that
> are global (ie inodes, dentries, etc). Only question I'd have is
> didn't Manfred or someone (Andi?) do this before? Or did that never
> get accepted? I know we talked about it a while back.
Are you thinking of the 2006-06-05 patch from Andi about using
the NUMA policy API for boot time allocation?
If so, that patch was accepted, but affects neither allocations
performed via alloc_bootmem nor __get_free_pages, which are
currently used to allocate these hashes. vmalloc, however, does
behave as desired with Andi's patch.
Which is why vmalloc was chosen to solve this problem. There were
other more complicated possible solutions (e.g. multi-level hash tables,
with the bottommost/largest level being allocated across all nodes),
however those would have been so intrusive as to be unpalatable.
So the vmalloc solution seemed reasonable, as long as it is used
only on architectures with plentiful vmalloc space.
Thanks,
Brent
--
Brent Casavant If you had nothing to fear,
bcasavan@sgi.com how then could you be brave?
Silicon Graphics, Inc. -- Queen Dama, Source Wars
--
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-14 19:30 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
2004-12-15 9:14 ` Andi Kleen
2004-12-14 23:24 ` Nick Piggin
2004-12-14 19:30 ` Brent Casavant [this message]
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=Pine.SGI.4.61.0412141319100.22462@kzerza.americas.sgi.com \
--to=bcasavan@sgi.com \
--cc=ak@suse.de \
--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