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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 04 Dec 2006 21:37:20 +0100
From:	Peter Zijlstra <peter@...gramming.kicks-ass.net>
To:	Andrew Morton <akpm@...l.org>
Cc:	Mel Gorman <mel@...net.ie>, clameter@....com,
	Linux Memory Management List <linux-mm@...ck.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andy Whitcroft <apw@...dowen.org>
Subject: Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that
	may be migrated

On Mon, 2006-12-04 at 11:30 -0800, Andrew Morton wrote:

> I'd also like to pin down the situation with lumpy-reclaim versus
> anti-fragmentation.  No offence, but I would of course prefer to avoid
> merging the anti-frag patches simply based on their stupendous size.  It
> seems to me that lumpy-reclaim is suitable for the e1000 problem, but
> perhaps not for the hugetlbpage problem.  Whereas anti-fragmentation adds
> vastly more code, but can address both problems?  Or something.

>>From my understanding they complement each other nicely. Without some
form of anti fragmentation there is no guarantee lumpy reclaim will ever
free really high order pages. Although it might succeed nicely for the
network sized allocations we now have problems with.

- Andy, do you have any number on non largepage order allocations? 

But anti fragmentation as per Mel's patches is not good enough to
provide largepage allocations since we would need to shoot down most of
the LRU to obtain such a large contiguous area. Lumpy reclaim however
can quickly achieve these sizes.

-
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