Re: [PATCH 7/13] Drain per-cpu lists when high-order allocations fail

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Nick Piggin <nickpiggin@...>
Cc: <akpm@...>, <linux-kernel@...>, <linux-mm@...>
Date: Tuesday, September 11, 2007 - 5:34 am

On Tue, 2007-09-11 at 01:05 +1000, Nick Piggin wrote:


Yes, it does help. It's noticable when one is trying to get as much
memory in hugepages as possible. It reaches a certain point where
hugepages are free but pinned due to per-cpu pages. This "certain point"
depends on the number of CPUs as a ratio to the size of physical memory
as well as a certain degree of randomness as the location of per-cpu
pages is not predictable. Worst case is not being able to allocate
something like (NR_CPUS * pcp->high * 2) hugepages even if they are
otherwise free.

By all means if you have a general version, send it and I'll take a
look. If it's more general and nicer but still can be used to drain the
per-cpu lists when high-order allocations fail, I'm all for it.

Thanks Nick



-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 8/13] Move free pages between lists on steal, Mel Gorman, (Mon Sep 10, 7:22 am)
Re: [PATCH 7/13] Drain per-cpu lists when high-order allocat..., Mel Gorman, (Tue Sep 11, 5:34 am)