From: John Stultz <john.stultz@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Robert Love <rlove@google.com>,
Christoph Hellwig <hch@infradead.org>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mel@csn.ul.ie>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>, Eric Anholt <eric@anholt.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] [RFC] fadvise: Add _VOLATILE,_ISVOLATILE, and _NONVOLATILE flags
Date: Tue, 22 Nov 2011 14:58:22 -0800 [thread overview]
Message-ID: <1322002702.6445.95.camel@work-vm> (raw)
In-Reply-To: <20111122133909.ebe72517.akpm@linux-foundation.org>
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@linaro.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
prev parent reply other threads:[~2011-11-22 22:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 3:33 [PATCH] [RFC] fadvise: Add _VOLATILE,_ISVOLATILE, and _NONVOLATILE flags John Stultz
2011-11-22 9:37 ` Rik van Riel
2011-11-22 10:45 ` Rik van Riel
2011-11-22 20:39 ` Dave Hansen
2011-11-22 16:31 ` Robert Love
2011-11-22 19:48 ` John Stultz
2011-11-23 0:27 ` Rik van Riel
[not found] ` <CAG6tG3xTkW1J=6xmUmmJoswJyR6ii5RDXvAsYrcH0CkVuUmJrQ@mail.gmail.com>
2011-11-23 0:39 ` Rik van Riel
2011-11-23 15:52 ` Robert Love
2011-11-26 0:05 ` Jan Kara
2011-11-22 20:52 ` Andrew Morton
2011-11-22 21:32 ` John Stultz
2011-11-22 21:39 ` Andrew Morton
2011-11-22 22:58 ` John Stultz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1322002702.6445.95.camel@work-vm \
--to=john.stultz@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=eric@anholt.net \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=rlove@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox