lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 13 Jul 2011 12:10:17 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] mm: page allocator: Reconsider zones for allocation
 after direct reclaim

On Wed, Jul 13, 2011 at 09:42:39AM +0900, KOSAKI Motohiro wrote:
> (2011/07/11 22:01), Mel Gorman wrote:
> > With zone_reclaim_mode enabled, it's possible for zones to be considered
> > full in the zonelist_cache so they are skipped in the future. If the
> > process enters direct reclaim, the ZLC may still consider zones to be
> > full even after reclaiming pages. Reconsider all zones for allocation
> > if direct reclaim returns successfully.
> > 
> > Signed-off-by: Mel Gorman <mgorman@...e.de>
> 
> Hmmm...
> 
> I like the concept, but I'm worry about a corner case a bit.
> 
> If users are using cpusets/mempolicy, direct reclaim don't scan all zones.
> Then, zlc_clear_zones_full() seems too aggressive operation.

As the system is likely to be running slow if it is in direct reclaim
that the complexity of being careful about which zone was cleared was
not worth it.

> Instead, couldn't we turn zlc->fullzones off from kswapd?
> 

Which zonelist should it clear (there are two) and when should it
happen? If it clears it on each cycle around balance_pgdat(), there
is no guarantee that it'll be cleared between when direct reclaim
finishes and an attempt is made to allocate.

-- 
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ