linux-kernel - Re: [PATCH] [RFC] fadvise: Add _VOLATILE,_ISVOLATILE, and

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, 22 Nov 2011 14:58:22 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Robert Love <rlove@...gle.com>,
	Christoph Hellwig <hch@...radead.org>,
	Hugh Dickins <hughd@...gle.com>, Mel Gorman <mel@....ul.ie>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Rik van Riel <riel@...hat.com>,
	Eric Anholt <eric@...olt.net>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH] [RFC] fadvise: Add _VOLATILE,_ISVOLATILE, and
 _NONVOLATILE flags

On Tue, 2011-11-22 at 13:39 -0800, Andrew Morton wrote:
> On Tue, 22 Nov 2011 13:32:18 -0800
> John Stultz <john.stultz@...aro.org> wrote:
> 
> > Very cool!  Yea. Dave brought up that the list was fairly inefficient,
> > but I figured I'd get more feedback on the mechanism before spending too
> > much time optimizing the structure. I'll look at your mumbletree code
> > and see how it can be adapted. Other then apparently being a nod to the
> > "original neo-grunge/indie-rock band from Rochester", is there a story
> > to the name? :)
> 
> I was first!

Sorry! Didn't realize it was the other way around. Hopefully reading the
code will inform my listening. :)

> I was sure there was some correct term for such a tree in the
> literature, but I didn't know what it was and the compiler didn't like
> "*_tree".
> 
> > Again, I appreciate the feedback! Thanks so much!
> 
> I note you sneakily deleted the bit about posix/bsd file locking.

Oh, no sneakiness intended. I agree about the parallels, and didn't
really have anything to add. Hopefully the needs here are a little bit
simpler, since we can coalesce regions. Maybe that will let us avoid the
worst of it?

thanks
-john


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