Hi,
> Before 0e093d99763e (writeback: do not sleep on the congestion queue if
> there are no congested BDIs or if significant congestion is not being
> encountered in the current zone), preferred_zone was only used for
> statistics and to determine the zoneidx from which to allocate from given
> the type requested.
True. So, following comment is now bogus. ;)
__alloc_pages_nodemask()
{
(snip)
get_mems_allowed();
/* The preferred zone is used for statistics later */
first_zones_zonelist(zonelist, high_zoneidx, nodemask, &preferred_zone);
if (!preferred_zone) {
put_mems_allowed();
return NULL;
}
Now, we have three preferred_zone usage.
1. for zone stat
2. wait_iff_congested
3. for calculate compaction duration
So, I have two question.
1. Why do we need different vm stat policy mempolicy and cpuset?
That said, if we are using mempolicy, the above nodemask variable is
not NULL, then preferrd_zone doesn't point nearest zone. But it point
always nearest zone when cpuset are used.
2. Why wait_iff_congested in page_alloc only wait preferred zone?
That said, theorically, any no congested zones in allocatable zones can
avoid waiting. Just code simplify?
3. I'm not sure why zone->compact_defer is not noted per zone, instead
noted only preferred zone. Do you know the intention?
I mean my first feeling tell me that we have a chance to make code simplify
more.
Mel, Can you please tell us your opinion?
> wait_iff_congested(), though, uses preferred_zone to determine if the
> congestion wait should be deferred because its dirty pages are backed by
> a congested bdi. This incorrectly defers the timeout and busy loops in
> the page allocator with various cond_resched() calls if preferred_zone is
> not allowed in the current context, usually consuming 100% of a cpu.
>
> This patch resets preferred_zone to an allowed zone in the slowpath if
> the allocation context is constrained by current's cpuset. It also
> ensures preferred_zone is from the set of allowed nodes when called from
> within direct reclaim; allocations are always constrainted by cpusets
> since the context is always blockable.
>
> Both of these uses of cpuset_current_mems_allowed are protected by
> get_mems_allowed().
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>