From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: vm/fs meetup in september? Date: Tue, 3 Jul 2007 01:04:18 +0200 Message-ID: <20070702230418.GA5630@lazybastard.org> References: <20070624042345.GB20033@wotan.suse.de> <6934efce0706251708h7ab8d7dal6682def601a82073@mail.gmail.com> <20070626060528.GA15134@infradead.org> <6934efce0706261007x5e402eebvc528d2d39abd03a3@mail.gmail.com> <20070630093243.GD22354@infradead.org> <6934efce0707021044x44f51337ofa046c85e342a973@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Christoph Hellwig , Nick Piggin , Linux Kernel Mailing List , Linux Memory Management List , linux-fsdevel@vger.kernel.org To: Jared Hulbert Return-path: Received: from lazybastard.de ([212.112.238.170]:47840 "EHLO longford.lazybastard.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756650AbXGBXNt (ORCPT ); Mon, 2 Jul 2007 19:13:49 -0400 Content-Disposition: inline In-Reply-To: <6934efce0707021044x44f51337ofa046c85e342a973@mail.gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 2 July 2007 10:44:00 -0700, Jared Hulbert wrote: >=20 > >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. >=20 > Maybe not. Yet, it would be a very useful place to store data from a > file as a non-volatile page cache. >=20 > Also it is something that I believe would benefit from a VFS-like API= =2E > I mean there is a consistent interface a management layer like this > could use, yet the algorithms used to order the data and the interfac= e > to the physical media may vary. There is no single right way to do > the management layer, much like filesystems. >=20 > Given the page orientation of the current VFS seems to me like there > might be a nice way to use it for this purpose. >=20 > 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 woul= d 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. J=C3=B6rn --=20 Joern's library part 5: http://www.faqs.org/faqs/compression-faq/part2/section-9.html - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html