LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: peter@chubb.wattle.id.au
To: Christoph Hellwig <hch@infradead.org>,
	Jared Hulbert <jaredeh@gmail.com>, 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: Sat, 30 Jun 2007 06:02:44 -0400	[thread overview]
Message-ID: <87bqexiwu3.wl%peter@chubb.wattle.id.au> (raw)
In-Reply-To: <20070630093243.GD22354@infradead.org>

>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:

Christoph> On Tue, Jun 26, 2007 at 10:07:24AM -0700, Jared Hulbert
Christoph> wrote:
>> If you have a large array of a non-volatile semi-writeable memory
>> such as a highspeed NOR Flash or some of the similar emerging
>> technologies in a system.  It would be useful to use that memory as
>> an extension of RAM.  One of the ways you could do that is allow
>> pages to be swapped out to this memory.  Once there these pages
>> could be read directly, but would require a COW procedure on a
>> write access.  The reason why I think this may be a vm/fs topic is
>> that the hardware makes writing to this memory efficiently a
>> non-trivial operation that requires management just like a
>> filesystem.  Also it seems to me that there are probably overlaps
>> between this topic and the recent filemap_xip.c discussions.

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.


You need either a block translation layer, or a (swap) filesystem that
understands flash peculiarities in order to make such a thing work.
The standard Linux swap format will not work.

--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia

  reply	other threads:[~2007-06-30 10:44 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 [this message]
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
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=87bqexiwu3.wl%peter@chubb.wattle.id.au \
    --to=peter@chubb.wattle.id.au \
    --cc=hch@infradead.org \
    --cc=jaredeh@gmail.com \
    --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).