From: "Jörn Engel" <joern@logfs.org>
To: Nick Piggin <npiggin@suse.de>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
Christoph Hellwig <hch@infradead.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: vm/fs meetup in september?
Date: Tue, 3 Jul 2007 01:09:15 +0200 [thread overview]
Message-ID: <20070702230914.GB5630@lazybastard.org> (raw)
In-Reply-To: <20070702061944.GA31557@wotan.suse.de>
On Mon, 2 July 2007 08:19:44 +0200, Nick Piggin wrote:
>
> Regarding numbers, there are about a dozen so far which is good
> but not as many filesystem maintainers as I had hoped (do they
> tend not to get invited to KS?). We may get a few more people yet
> so I think if we try to get a room to fit 20-25 people it would
> be ideal: I don't want to turn anyone away ;)
I'm interested.
My particular pet subject would be sync behaviour. LogFS benefits from
writing data in a particular order - data first, then indirect blocks,
doubly indirect, triply, etc. Reason is that indirect blocks get
dirtied when data is written.
The current solution is to write indirect blocks immediatly, causing
quite bad performance.
JA?rn
--
Measure. Don't tune for speed until you've measured, and even then
don't unless one part of the code overwhelms the rest.
-- Rob Pike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-02 23:09 UTC|newest]
Thread overview: 23+ 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-07-02 6:19 ` Nick Piggin
2007-07-02 23:09 ` Jörn Engel [this message]
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
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=20070702230914.GB5630@lazybastard.org \
--to=joern@logfs.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=nickpiggin@yahoo.com.au \
--cc=npiggin@suse.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox