[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6934efce0707021026wad68bbar2d239d0cb7954ea0@mail.gmail.com>
Date: Mon, 2 Jul 2007 10:26:13 -0700
From: "Jared Hulbert" <jaredeh@...il.com>
To: "Al Boldi" <a1426z@...ab.com>
Cc: peter@...bb.wattle.id.au, "Christoph Hellwig" <hch@...radead.org>,
"Nick Piggin" <npiggin@...e.de>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Linux Memory Management List" <linux-mm@...ck.org>,
linux-fsdevel@...r.kernel.org
Subject: Re: vm/fs meetup in september?
> > 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.
-
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/
Powered by blists - more mailing lists