linux-kernel - Re: [PATCH 0/13] Reduce external fragmentation by grouping pages by mobility v30

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:	Fri, 14 Sep 2007 15:33:55 +0100
From:	mel@...net.ie (Mel Gorman)
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 0/13] Reduce external fragmentation by grouping pages by mobility v30

On (13/09/07 18:01), Andrew Morton didst pronounce:
> On Mon, 10 Sep 2007 12:20:11 +0100 (IST) Mel Gorman <mel@....ul.ie> wrote:
> 
> > Here is a restacked version of the grouping pages by mobility patches
> > based on the patches currently in your tree. It should be  a drop-in
> > replacement for what is in 2.6.23-rc4-mm1 and is what I propose for merging
> > to mainline.
> 
> It really gives me the creeps to throw away a large set of large patches
> and to then introduce a new set.
> 

I can understand that logic.

> What would go wrong if we just merged the patches I already have?
> 

Nothing, the end result is more or less the same. There are three style
cleanups in the restack and for some reason, one of the functions moved
but otherwise they are identical.

The restacked version was provided to illustrate what the final stack really
looks like and because I thought you would prefer it over a stack that had
one patch introducing a change and a later patch removing it (like making
it configurable for example). It also allowed us to test against mainline
to make sure everything was ok prior to the merge.

Go ahead with the patches you already
have if you prefer. Just make sure not to include
breakout-page_order-to-internalh-to-avoid-special-knowledge-of-the-buddy-allocator.patch
as it's only required for page-owner-tracking.

Thanks Andrew.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
-
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/