linux-kernel - Re: vm/fs meetup in september?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Jun 2007 10:07:24 -0700
From:	"Jared Hulbert" <jaredeh@...il.com>
To:	"Christoph Hellwig" <hch@...radead.org>,
	"Jared Hulbert" <jaredeh@...il.com>,
	"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?

On 6/25/07, Christoph Hellwig <hch@...radead.org> wrote:
> On Mon, Jun 25, 2007 at 05:08:02PM -0700, Jared Hulbert wrote:
> > -memory mappable swap file (I'm not sure if this one is appropriate
> > for the proposed meeting)
>
> Please explain what this is supposed to mean.

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.
-
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/