linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Con Kolivas <kernel@kolivas.org>,
	linux-mm@kvack.org, Andrew Morton <akpm@osdl.org>,
	ck@vds.kolivas.org
Subject: Re: [PATCH] mm: implement swap prefetching
Date: Tue, 7 Feb 2006 23:39:08 +0100	[thread overview]
Message-ID: <200602072339.09327.ak@suse.de> (raw)
In-Reply-To: <20060207203420.GA10493@dmt.cnet>

On Tuesday 07 February 2006 21:34, Marcelo Tosatti wrote:
> On Tue, Feb 07, 2006 at 05:51:27PM +1100, Nick Piggin wrote:
> > Con Kolivas wrote:
> > >On Tue, 7 Feb 2006 04:00 pm, Nick Piggin wrote:
> > >
> > >>Con Kolivas wrote:
> > >>
> > >>>On Tue, 7 Feb 2006 02:08 pm, Nick Piggin wrote:
> > >>>
> > >>>>prefetch_get_page is doing funny things with zones and nodes / zonelists
> > >>>>(eg. 'We don't prefetch into DMA' meaning something like 'this only 
> > >>>>works
> > >>>>on i386 and x86-64').
> > >>>
> > >>>Hrm? It's just a generic thing to do; I'm not sure I follow why it's i386
> > >>>and x86-64 only. Every architecture has ZONE_NORMAL so it will prefetch
> > >>>there.
> > >>
> > >>I don't think every architecture has ZONE_NORMAL.
> > >
> > >
> > >!ZONE_DMA they all have, no?
> > >
> > 
> > Don't think so. IIRC ppc64 has only ZONE_DMA although may have picked up
> > DMA32 now (/me boots the G5). IA64 I think have 4GB ZONE_DMA so smaller
> > systems won't have any other zones.
> > 
> > On small memory systems, ZONE_DMA will be a significant portion of memory
> > too (but maybe you're not targetting them either).
> 
> embedded 32-bit PPC's have all their memory in DMA:

Most x86-64 systems have their memory in ZONE_DMA32 now. Only large ones
have any ZONE_NORMAL >4GB. So it's not even true on x86-64 :)

-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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-02-07 22:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 23:28 Con Kolivas
2006-02-07  0:38 ` Andrew Morton
2006-02-07  1:29   ` Con Kolivas
2006-02-07  1:32     ` [ck] " Con Kolivas
2006-02-07  1:39     ` Andrew Morton
2006-02-08  3:29   ` [PATCH] mm: implement swap prefetching v21 Con Kolivas
2006-02-08  3:49     ` [ck] " Con Kolivas
2006-02-07  3:08 ` [PATCH] mm: implement swap prefetching Nick Piggin
2006-02-07  3:29   ` Nick Piggin
2006-02-07  4:02   ` Con Kolivas
2006-02-07  5:00     ` Nick Piggin
2006-02-07  6:02       ` Con Kolivas
2006-02-07  6:51         ` Nick Piggin
2006-02-07 10:54           ` Con Kolivas
2006-02-07 17:14             ` Andrew Morton
2006-02-07 20:34           ` Marcelo Tosatti
2006-02-07 22:39             ` Andi Kleen [this message]
2006-02-08  4:46     ` Paul Jackson
2006-02-08  5:06       ` Con Kolivas
2006-02-08  5:13         ` Paul Jackson
2006-02-08  5:33         ` Con Kolivas
2006-02-24 11:23 [PATCH] mm: Implement " Con Kolivas

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=200602072339.09327.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=nickpiggin@yahoo.com.au \
    /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