linux-kernel - Re: [PATCH 0/8] Use memory compaction instead of lumpy reclaim during high-order allocations

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] [day] [month] [year] [list]

Date:	Fri, 19 Nov 2010 10:45:40 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Mel Gorman <mel@....ul.ie>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Johannes Weiner <hannes@...xchg.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Andrea Arcangeli <aarcange@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Rik van Riel <riel@...hat.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8] Use memory compaction instead of lumpy reclaim
 during high-order allocations

On Fri, Nov 19, 2010 at 02:05:32PM +0000, Mel Gorman wrote:
> > 
> > How about making the default before 2.6.40, as an initial step?
> > 
> 
> It'd be a reasonable way of ensuring it's being tested everywhere
> and not by those that are interested or using distro kernel configs.
> I guess we'd set to "default y" in the same patch that adds the note to
> feature-removal-schedule.txt.

I'd suggest doing it now (or soon, before 2.6.40), just to make sure
there aren't massive complaints about performance regressions, etc.,
and then deprecating it at say 2.6.42, and then waiting 6-9 months
before removing it.  But, I'm a bit more conservative about making
such changes.

(Said the person who has reluctantly agreed to keep the minixdf mount
option after we found users when we tried deprecating it.  :-)

       	     	      	    	    	  - Ted
--
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/