From: Christoph Lameter <clameter@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Mel Gorman <mel@skynet.ie>,
Lee.Schermerhorn@hp.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 3/4] Embed zone_id information within the zonelist->zones pointer
Date: Mon, 13 Aug 2007 14:25:36 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708131423050.28026@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200708110304.55433.ak@suse.de>
On Sat, 11 Aug 2007, Andi Kleen wrote:
> > Hallelujah. You are my hero! x86_64 will switch off CONFIG_ZONE_DMA?
>
> Yes. i386 too actually.
>
> The DMA zone will be still there, but only reachable with special functions.
Not too happy with that one but this is going the right direcrtion.
On NUMA this would still mean allocating space for the DMA zone on all
nodes although we only need this on node 0.
> Also all callers are going to pass masks around so it's always clear
> what address range they really need. Actually a lot of them
> pass still 16MB simply because it is hard to find out what masks
> old undocumented hardware really needs. But this could change.
Good.
> This also means the DMA support in sl[a-z]b is not needed anymore.
Tell me when. SLUB has an #ifdef CONFIG_ZONE_DMA. We can just drop that
code in the #ifdef's if you are ready.
> I went through near all GFP_DMA users and found they're usually
> happy enough with pages. If someone comes up who really needs
> lots of subobjects the right way for them would be likely extending
> the pci pool allocator for this case. But I haven't found a need for this yet.
Great.
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-08-13 21:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 21:06 [PATCH 0/4] Use one zonelist per node instead of multiple zonelists v3 Mel Gorman
2007-08-09 21:06 ` [PATCH 1/4] Use zonelists instead of zones when direct reclaiming pages Mel Gorman
2007-08-09 21:19 ` Christoph Lameter
2007-08-09 21:06 ` [PATCH 2/4] Use one zonelist that is filtered instead of multiple zonelists Mel Gorman
2007-08-09 21:27 ` Christoph Lameter
2007-08-09 21:07 ` [PATCH 3/4] Embed zone_id information within the zonelist->zones pointer Mel Gorman
2007-08-09 21:37 ` Christoph Lameter
2007-08-09 23:33 ` Mel Gorman
2007-08-10 1:44 ` Christoph Lameter
2007-08-10 10:47 ` Mel Gorman
2007-08-10 17:37 ` Christoph Lameter
2007-08-10 18:13 ` Andi Kleen
2007-08-10 19:02 ` Christoph Lameter
2007-08-11 1:04 ` Andi Kleen
2007-08-13 21:25 ` Christoph Lameter [this message]
2007-08-13 22:50 ` Andi Kleen
2007-08-13 22:00 ` Christoph Lameter
2007-08-13 22:58 ` Andi Kleen
2007-08-13 22:09 ` Christoph Lameter
2007-08-13 23:08 ` Andi Kleen
2007-08-13 22:22 ` Christoph Lameter
2007-08-13 23:42 ` Andi Kleen
2007-08-13 22:52 ` Christoph Lameter
2007-08-13 23:55 ` Andi Kleen
2007-08-13 23:12 ` Christoph Lameter
2007-08-14 0:16 ` Andi Kleen
2007-08-13 23:25 ` Christoph Lameter
2007-08-14 0:25 ` Andi Kleen
2007-08-13 22:38 ` Christoph Lameter
2007-08-13 23:43 ` Andi Kleen
2007-08-13 22:54 ` Christoph Lameter
2007-08-14 0:00 ` Andi Kleen
2007-08-13 23:16 ` Christoph Lameter
2007-08-14 0:16 ` Andi Kleen
2007-08-13 23:27 ` Christoph Lameter
2007-08-14 0:26 ` Andi Kleen
2007-08-14 19:56 ` Christoph Lameter
2007-08-13 23:22 ` Alan Cox
2007-08-14 0:14 ` Andi Kleen
2007-08-13 23:44 ` Alan Cox
2007-08-14 19:11 ` Andy Isaacson
2007-08-14 20:23 ` Andi Kleen
2007-08-14 19:43 ` Andy Isaacson
2007-08-14 21:05 ` Andi Kleen
2007-08-15 11:37 ` Ralf Baechle
2007-08-15 12:59 ` Andi Kleen
2007-08-15 12:32 ` Ralf Baechle
2007-08-15 19:59 ` Christoph Lameter
2007-08-09 21:07 ` [PATCH 4/4] Apply MPOL_BIND policy to two highest zones when highest is ZONE_MOVABLE Mel Gorman
2007-08-09 21:37 ` Christoph Lameter
2007-08-09 21:19 ` [PATCH 0/4] Use one zonelist per node instead of multiple zonelists v3 Christoph Lameter
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.LNX.4.64.0708131423050.28026@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
/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