linux-kernel - Re: [patch 10/19] No Reclaim LRU Infrastructure

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:	Tue, 15 Jan 2008 09:06:20 +0900
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Lee Schermerhorn <Lee.Schermerhorn@...com>
Cc:	kosaki.motohiro@...fujitsu.com, Rik van Riel <riel@...hat.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [patch 10/19] No Reclaim LRU Infrastructure

Hi Lee-san

> > > +config NORECLAIM
> > > +	bool "Track non-reclaimable pages (EXPERIMENTAL; 64BIT only)"
> > > +	depends on EXPERIMENTAL && 64BIT
> > > +	help
> > > +	  Supports tracking of non-reclaimable pages off the [in]active lists
> > > +	  to avoid excessive reclaim overhead on large memory systems.  Pages
> > > +	  may be non-reclaimable because:  they are locked into memory, they
> > > +	  are anonymous pages for which no swap space exists, or they are anon
> > > +	  pages that are expensive to unmap [long anon_vma "related vma" list.]
> > 
> > Why do you select to default is NO ?
> > I think this is really improvement and no one of 64bit user
> > hope turn off without NORECLAIM developer :)
> 
> This was my doing.  I left the default == NO during
> development/experimemental stage so that one would have to take explicit
> action to enable this function.  If the feature makes it into mainline
> and we decide that the default should be 'yes', that will be an easy
> change.

Oh I see.
I will help testing too for it merges to mainline early. 

thanks.


- kosaki


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