Re: Interacting with coherent memory on external devices

From: Vlastimil Babka
Date: Thu May 14 2015 - 03:39:23 EST

On 05/14/2015 01:38 AM, Benjamin Herrenschmidt wrote:
On Wed, 2015-05-13 at 16:10 +0200, Vlastimil Babka wrote:
Sorry for reviving oldish thread...

Well, that's actually appreciated since this is constructive discussion
of the kind I was hoping to trigger initially :-) I'll look at

I hoped so :)

ZONE_MOVABLE, I wasn't aware of its existence.

Don't we still have the problem that ZONEs must be somewhat contiguous
chunks ? Ie, my "CAPI memory" will be interleaved in the physical
address space somewhat.. This is due to the address space on some of
those systems where you'll basically have something along the lines of:

[ node 0 mem ] [ node 0 CAPI dev ] .... [ node 1 mem] [ node 1 CAPI dev] ...

Oh, I see. The VM code should cope with that, but some operations would be inefficiently looping over the holes in the CAPI zone by 2MB pageblock per iteration. This would include compaction scanning, which would suck if you need those large contiguous allocations as you said. Interleaving works better if it's done with a smaller granularity.

But I guess you could just represent the CAPI as multiple NUMA nodes, each with single ZONE_MOVABLE zone. Especially if "node 0 CAPI dev" and "node 1 CAPI dev" differs in other characteristics than just using a different range of PFNs... otherwise what's the point of this split anyway?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at