LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"Nick Piggin" <npiggin@suse.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: vm/fs meetup in september?
Date: Mon, 2 Jul 2007 17:46:40 -0700 [thread overview]
Message-ID: <6934efce0707021746q133c62f5l803e5fa78b3535d9@mail.gmail.com> (raw)
In-Reply-To: <20070702230418.GA5630@lazybastard.org>
On 7/2/07, Jörn Engel <joern@logfs.org> wrote:
> On Mon, 2 July 2007 10:44:00 -0700, Jared Hulbert wrote:
> >
> > >So what you mean is "swap on flash" ? Defintively sounds like an
> > >interesting topic, although I'm not too sure it's all that
> > >filesystem-related.
> >
> > Maybe not. Yet, it would be a very useful place to store data from a
> > file as a non-volatile page cache.
> >
> > Also it is something that I believe would benefit from a VFS-like API.
> > I mean there is a consistent interface a management layer like this
> > could use, yet the algorithms used to order the data and the interface
> > to the physical media may vary. There is no single right way to do
> > the management layer, much like filesystems.
> >
> > Given the page orientation of the current VFS seems to me like there
> > might be a nice way to use it for this purpose.
> >
> > Or maybe the real experts on this stuff can tell me how wrong that is
> > and where it should go :)
>
> I don't believe anyone has implemented this before, so any experts would
> be self-appointed.
>
> Maybe this should be turned into a filesystem subject after all. The
> complexity comes from combining XIP with writes on the same chip. So
> solving your problem should be identical to solving the rw XIP
> filesystem problem.
>
> If there is interest in the latter, I'd offer my self-appointed
> expertise.
Right, the solution to swap problem is identical to the rw XIP
filesystem problem. Jörn, that's why you're the self-appointed
subject matter expert!
next prev parent reply other threads:[~2007-07-03 0:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 4:23 Nick Piggin
2007-06-25 6:35 ` Christoph Hellwig
2007-06-25 17:26 ` Zach Brown
2007-06-26 2:35 ` Nick Piggin
2007-06-26 3:23 ` Andreas Dilger
2007-06-26 12:38 ` Chris Mason
2007-06-30 9:31 ` Christoph Hellwig
2007-06-30 12:35 ` Martin J. Bligh
2007-06-26 0:08 ` Jared Hulbert
2007-06-26 6:05 ` Christoph Hellwig
2007-06-26 17:07 ` Jared Hulbert
2007-06-30 9:32 ` Christoph Hellwig
2007-06-30 10:02 ` peter
2007-06-30 10:09 ` Christoph Hellwig
2007-06-30 21:58 ` Al Boldi
2007-07-02 17:26 ` Jared Hulbert
2007-07-02 17:44 ` Jared Hulbert
2007-07-02 23:04 ` Jörn Engel
2007-07-03 0:46 ` Jared Hulbert [this message]
2007-07-03 12:25 ` Jörn Engel
2007-07-04 0:28 ` Dongjun Shin
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=6934efce0707021746q133c62f5l803e5fa78b3535d9@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=hch@infradead.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--subject='Re: vm/fs meetup in september?' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).