From: Mel Gorman <mel@csn.ul.ie>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Adam Litke <agl@us.ibm.com>, Avi Kivity <avi@redhat.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 05/12] Memory compaction core
Date: Tue, 16 Feb 2010 14:59:44 +0000 [thread overview]
Message-ID: <20100216145943.GA997@csn.ul.ie> (raw)
In-Reply-To: <alpine.DEB.2.00.1002160849460.18275@router.home>
On Tue, Feb 16, 2010 at 08:55:46AM -0600, Christoph Lameter wrote:
> On Tue, 16 Feb 2010, Mel Gorman wrote:
>
> > Because how do I tell in advance that the data I am migrating from DMA can
> > be safely relocated to the NORMAL zone? We don't save GFP flags. Granted,
> > for DMA, that will not matter as pages that must be in DMA will also not by
> > migratable. However, buffer pages should not get relocated to HIGHMEM for
> > example which is more likely to happen. It could be special cased but
> > I'm not aware of ZONE_DMA-related pressure problems that would make this
> > worthwhile and if so, it should be handled as a separate patch series.
>
> Oh there are numerous ZONE_DMA pressure issues if you have ancient /
> screwed up hardware that can only operate on DMA or DMA32 memory.
>
I've never ran into the issue. I was under the impression that the only
device that might care these days are floopy disks.
> Moving page cache pages out of the DMA zone would be good. A
> write request will cause the page to bounce back to the DMA zone if the
> device requires the page there.
>
> But I also think that the patchset should be as simple as possible so that
> it can be merged soon.
>
Agreed.
> > Ah, it was 2009 when I last kicked this around heavily :) I'll update
> > it.
>
> But it was authored in 2009. May be important if patent or other
> copyright claims arise. 2009-2010?
>
2007-2010 in that case because 2007 was when I first prototyped this.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mel@csn.ul.ie>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Adam Litke <agl@us.ibm.com>, Avi Kivity <avi@redhat.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 05/12] Memory compaction core
Date: Tue, 16 Feb 2010 14:59:44 +0000 [thread overview]
Message-ID: <20100216145943.GA997@csn.ul.ie> (raw)
In-Reply-To: <alpine.DEB.2.00.1002160849460.18275@router.home>
On Tue, Feb 16, 2010 at 08:55:46AM -0600, Christoph Lameter wrote:
> On Tue, 16 Feb 2010, Mel Gorman wrote:
>
> > Because how do I tell in advance that the data I am migrating from DMA can
> > be safely relocated to the NORMAL zone? We don't save GFP flags. Granted,
> > for DMA, that will not matter as pages that must be in DMA will also not by
> > migratable. However, buffer pages should not get relocated to HIGHMEM for
> > example which is more likely to happen. It could be special cased but
> > I'm not aware of ZONE_DMA-related pressure problems that would make this
> > worthwhile and if so, it should be handled as a separate patch series.
>
> Oh there are numerous ZONE_DMA pressure issues if you have ancient /
> screwed up hardware that can only operate on DMA or DMA32 memory.
>
I've never ran into the issue. I was under the impression that the only
device that might care these days are floopy disks.
> Moving page cache pages out of the DMA zone would be good. A
> write request will cause the page to bounce back to the DMA zone if the
> device requires the page there.
>
> But I also think that the patchset should be as simple as possible so that
> it can be merged soon.
>
Agreed.
> > Ah, it was 2009 when I last kicked this around heavily :) I'll update
> > it.
>
> But it was authored in 2009. May be important if patent or other
> copyright claims arise. 2009-2010?
>
2007-2010 in that case because 2007 was when I first prototyped this.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2010-02-16 15:00 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 12:00 [PATCH 0/12] Memory Compaction v2r12 Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-12 12:00 ` [PATCH 01/12] mm: Document /proc/pagetypeinfo Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-12 15:54 ` Christoph Lameter
2010-02-12 15:54 ` Christoph Lameter
2010-02-16 7:05 ` KOSAKI Motohiro
2010-02-16 7:05 ` KOSAKI Motohiro
2010-02-12 12:00 ` [PATCH 02/12] Allow CONFIG_MIGRATION to be set without CONFIG_NUMA or memory hot-remove Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-16 17:43 ` Rik van Riel
2010-02-16 17:43 ` Rik van Riel
2010-02-12 12:00 ` [PATCH 03/12] Export unusable free space index via /proc/pagetypeinfo Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-16 7:03 ` KOSAKI Motohiro
2010-02-16 7:03 ` KOSAKI Motohiro
2010-02-16 8:36 ` Mel Gorman
2010-02-16 8:36 ` Mel Gorman
2010-02-16 8:41 ` KOSAKI Motohiro
2010-02-16 8:41 ` KOSAKI Motohiro
2010-02-16 8:50 ` Mel Gorman
2010-02-16 8:50 ` Mel Gorman
2010-02-16 18:28 ` Rik van Riel
2010-02-16 18:28 ` Rik van Riel
2010-02-18 15:23 ` Minchan Kim
2010-02-18 15:23 ` Minchan Kim
2010-02-18 15:32 ` Mel Gorman
2010-02-18 15:32 ` Mel Gorman
2010-02-12 12:00 ` [PATCH 04/12] Export fragmentation " Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-16 7:59 ` KOSAKI Motohiro
2010-02-16 7:59 ` KOSAKI Motohiro
2010-02-16 8:41 ` Mel Gorman
2010-02-16 8:41 ` Mel Gorman
2010-02-16 8:49 ` KOSAKI Motohiro
2010-02-16 8:49 ` KOSAKI Motohiro
2010-02-17 1:44 ` Rik van Riel
2010-02-17 1:44 ` Rik van Riel
2010-02-18 15:37 ` Minchan Kim
2010-02-18 15:37 ` Minchan Kim
2010-02-12 12:00 ` [PATCH 05/12] Memory compaction core Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-16 8:31 ` KOSAKI Motohiro
2010-02-16 8:31 ` KOSAKI Motohiro
2010-02-16 8:48 ` Mel Gorman
2010-02-16 8:48 ` Mel Gorman
2010-02-16 14:55 ` Christoph Lameter
2010-02-16 14:55 ` Christoph Lameter
2010-02-16 14:59 ` Mel Gorman [this message]
2010-02-16 14:59 ` Mel Gorman
2010-02-18 19:37 ` Christoph Lameter
2010-02-18 19:37 ` Christoph Lameter
2010-02-18 21:35 ` Mel Gorman
2010-02-18 21:35 ` Mel Gorman
2010-02-19 0:04 ` KAMEZAWA Hiroyuki
2010-02-19 0:04 ` KAMEZAWA Hiroyuki
2010-02-17 13:29 ` Mel Gorman
2010-02-17 13:29 ` Mel Gorman
2010-02-17 15:45 ` Rik van Riel
2010-02-17 15:45 ` Rik van Riel
2010-02-18 16:58 ` Minchan Kim
2010-02-18 16:58 ` Minchan Kim
2010-02-18 17:34 ` Mel Gorman
2010-02-18 17:34 ` Mel Gorman
2010-02-19 1:21 ` Minchan Kim
2010-02-19 1:21 ` Minchan Kim
2010-02-19 14:33 ` Mel Gorman
2010-02-19 14:33 ` Mel Gorman
2010-02-12 12:00 ` [PATCH 06/12] Add /proc trigger for memory compaction Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-12 18:34 ` Valdis.Kletnieks
2010-02-12 18:38 ` Mel Gorman
2010-02-12 18:38 ` Mel Gorman
2010-02-17 16:30 ` Rik van Riel
2010-02-17 16:30 ` Rik van Riel
2010-02-18 19:51 ` Christoph Lameter
2010-02-18 19:51 ` Christoph Lameter
2010-02-19 1:56 ` Minchan Kim
2010-02-19 1:56 ` Minchan Kim
2010-02-12 12:00 ` [PATCH 07/12] Add /sys trigger for per-node " Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-17 16:30 ` Rik van Riel
2010-02-17 16:30 ` Rik van Riel
2010-02-12 12:00 ` [PATCH 08/12] Direct compact when a high-order allocation fails Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-18 3:57 ` Rik van Riel
2010-02-18 3:57 ` Rik van Riel
2010-02-12 12:00 ` [PATCH 09/12] Do not compact within a preferred zone after a compaction failure Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-18 4:09 ` Rik van Riel
2010-02-18 4:09 ` Rik van Riel
2010-02-12 12:00 ` [PATCH 10/12] mm: Check for an empty VMA list in rmap_walk_anon Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-17 18:22 ` Mel Gorman
2010-02-17 18:22 ` Mel Gorman
2010-02-12 12:00 ` [PATCH 11/12] mm: Take the RCU read lock " Mel Gorman
2010-02-12 12:00 ` Mel Gorman
2010-02-12 12:00 ` [PATCH 12/12] mm: Check the anon_vma is still valid in rmap_walk_anon() Mel Gorman
2010-02-12 12:00 ` Mel Gorman
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=20100216145943.GA997@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=aarcange@redhat.com \
--cc=agl@us.ibm.com \
--cc=avi@redhat.com \
--cc=cl@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.