Re: [PATCH 4/9] mm: MIGRATE_CMA migration type added
From: Michal Nazarewicz
Date: Thu Oct 27 2011 - 05:10:49 EST
On Tue, 18 Oct 2011 06:08:26 -0700, Mel Gorman <mel@xxxxxxxxx> wrote:
This does mean that MIGRATE_CMA also does not have a per-cpu list.
I don't know if that matters to you but all allocations using
MIGRATE_CMA will take the zone lock.
On Mon, 24 Oct 2011 21:32:45 +0200, Michal Nazarewicz <mina86@xxxxxxxxxx> wrote:
This is sort of an artefact of my misunderstanding of pcp lists in the
past. I'll have to re-evaluate the decision not to include CMA on pcp
Actually sorry. My comment above is somehow invalid.
The CMA does not need to be on pcp list because CMA pages are never allocated
via standard kmalloc() and friends. Because of the fallbacks in rmqueue_bulk()
the CMA pages end up being added to a pcp list of the MOVABLE type and so when
kmallec() allocates an MOVABLE page it can end up grabbing a CMA page.
So it's quite OK that CMA does not have its own pcp list as the list would
not be used anyway.
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, MichaÅ âmina86â Nazarewicz (o o)
ooo +----<email/xmpp: mpn@xxxxxxxxxx>--------------ooO--(_)--Ooo--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/