LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Nick Piggin" <npiggin@suse.de>
Cc: "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: Mon, 25 Jun 2007 17:08:02 -0700 [thread overview]
Message-ID: <6934efce0706251708h7ab8d7dal6682def601a82073@mail.gmail.com> (raw)
In-Reply-To: <20070624042345.GB20033@wotan.suse.de>
> 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)
next prev parent reply other threads:[~2007-06-26 0:08 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 [this message]
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
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=6934efce0706251708h7ab8d7dal6682def601a82073@mail.gmail.com \
--to=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).