linux-kernel - Re: [PATCH resend] drop_caches: add some documentation and info message

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, 30 Jul 2013 16:47:15 +0200
From:	Michal Hocko <mhocko@...e.cz>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	dave.hansen@...el.com, kosaki.motohiro@...fujitsu.com,
	kamezawa.hiroyu@...fujitsu.com, bp@...e.de,
	Dave Hansen <dave@...ux.vnet.ibm.com>
Subject: Re: [PATCH resend] drop_caches: add some documentation and info
 message

On Tue 30-07-13 07:39:56, Andrew Morton wrote:
> On Tue, 30 Jul 2013 14:55:25 +0200 Michal Hocko <mhocko@...e.cz> wrote:
> 
> > > > I am OK with that  but can we use a top bit instead. Maybe we never have
> > > > other entities to drop in the future but it would be better to have a room for them
> > > > just in case.
> > > 
> > > If we add another flag in the future it can use bit 3?
> > 
> > What if we get crazy and need more of them?
> 
> Then we use bit 4.  Then 5.  Then 6.
> 
> I'm really not understanding your point here ;)

I meant let's keep entities to drop in the low bits and the mode of
printing in the top so they are separated.

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