From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jared Hulbert" Subject: Re: vm/fs meetup in september? Date: Mon, 25 Jun 2007 17:08:02 -0700 Message-ID: <6934efce0706251708h7ab8d7dal6682def601a82073@mail.gmail.com> References: <20070624042345.GB20033@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Linux Kernel Mailing List" , "Linux Memory Management List" , linux-fsdevel@vger.kernel.org To: "Nick Piggin" Return-path: Received: from wa-out-1112.google.com ([209.85.146.180]:24513 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751100AbXFZAID (ORCPT ); Mon, 25 Jun 2007 20:08:03 -0400 Received: by wa-out-1112.google.com with SMTP id v27so2038580wah for ; Mon, 25 Jun 2007 17:08:03 -0700 (PDT) In-Reply-To: <20070624042345.GB20033@wotan.suse.de> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > A few things I'd like to talk about are: > > - the address space operations APIs, and their page based nature. I think > it would be nice to generally move toward offset,length based ones as > much as possible because it should give more efficiency and flexibility > in the filesystem. > > - write_begin API if it is still an issue by that date. Hope not :) > > - truncate races > > - fsblock if it hasn't been shot down by then > > - how to make complex API changes without having to fix most things > yourself. I'd like to add: -revamping filemap_xip.c -memory mappable swap file (I'm not sure if this one is appropriate for the proposed meeting)