LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Al Boldi" <a1426z@gawab.com>
Cc: peter@chubb.wattle.id.au, "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 10:26:13 -0700	[thread overview]
Message-ID: <6934efce0707021026wad68bbar2d239d0cb7954ea0@mail.gmail.com> (raw)
In-Reply-To: <200706301758.16607.a1426z@gawab.com>

> > Christoph> So what you mean is "swap on flash" ?  Defintively sounds
> > Christoph> like an interesting topic, although I'm not too sure it's
> > Christoph> all that filesystem-related.
>
> I wouldn't want to call it swap, as this carries with it block-io
> connotations.  It's really mmap on flash.

Yes it is really mmap on flash.  But you are "swapping" pages from RAM
to be mmap'ed on flash.  Also the flash-io complexities are similar to
the block-io layer.  I think "swap on flash" is fair.  Though that
might be confused with making swap work on a NAND flash, which is very
much like the current block-io approach.  "Mmappable swap on flash" is
more exact, I suppose.

> > You need either a block translation layer,
>
> Are you suggesting to go through the block layer to reach the flash?

Well the obvious route would be to have this management layer use the
MTD, I can't see anything wrong with that.

> > or a (swap) filesystem that
> > understands flash peculiarities in order to make such a thing work.
> > The standard Linux swap format will not work.
>
> Correct.
>
> BTW, you may want to have a look at my "[RFC] VM: I have a dream..." thread.

Interesting.  This idea does allow for swap to be access directly.

  reply	other threads:[~2007-07-02 17:26 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 [this message]
2007-07-02 17:44         ` Jared Hulbert
2007-07-02 23:04           ` Jörn Engel
2007-07-03  0:46             ` Jared Hulbert
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=6934efce0707021026wad68bbar2d239d0cb7954ea0@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=a1426z@gawab.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=peter@chubb.wattle.id.au \
    --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).