From: Artem Bityutskiy <dedekind@infradead.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, akpm@osdl.org,
David Woodhouse <dwmw2@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: LogFS take five
Date: Wed, 08 Aug 2007 19:52:00 +0300 [thread overview]
Message-ID: <1186591920.19606.45.camel@sauron> (raw)
In-Reply-To: <20070808163545.GU15319@lazybastard.org>
On Wed, 2007-08-08 at 18:35 +0200, Jörn Engel wrote:
> Scanning. I don't have seperate accounting yet.
Ok, but how are you going to implement it? Surely you cannot say that
LogFS is scalable before you have better space accounting (or you at
least should note that it is scalable up to some limit).
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-08-08 16:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 16:12 LogFS take five Jörn Engel
2007-08-08 16:13 ` [Patch 01/18] fs/logfs/Makefile Jörn Engel
2007-08-08 16:14 ` [Patch 02/18] include/linux/logfs.h Jörn Engel
2007-08-08 22:56 ` Arnd Bergmann
2007-08-09 20:03 ` Jörn Engel
2007-08-08 16:15 ` [Patch 03/18] fs/logfs/logfs.h Jörn Engel
2007-08-08 16:15 ` [Patch 04/18] fs/logfs/compr.c Jörn Engel
2007-08-08 16:16 ` [Patch 05/18] fs/logfs/dir.c Jörn Engel
2007-08-08 17:07 ` Artem Bityutskiy
2007-08-08 17:15 ` Jörn Engel
2007-08-08 17:34 ` Artem Bityutskiy
2007-08-08 17:41 ` Jörn Engel
2007-08-08 18:50 ` Artem Bityutskiy
2007-08-08 16:17 ` [Patch 05/18] fs/logfs/file.c Jörn Engel
2007-08-08 16:17 ` [Patch 07/18] fs/logfs/gc.c Jörn Engel
2007-08-08 16:18 ` [Patch 08/18] fs/logfs/inode.c Jörn Engel
2007-08-08 16:19 ` [Patch 08/18] fs/logfs/journal.c Jörn Engel
2007-08-08 16:19 ` [Patch 10/18] fs/logfs/memtree.c Jörn Engel
2007-08-08 16:20 ` [Patch 11/18] fs/logfs/readwrite.c Jörn Engel
2007-08-08 16:20 ` [Patch 12/18] fs/logfs/segment.c Jörn Engel
2007-08-08 16:21 ` [Patch 13/18] fs/logfs/super.c Jörn Engel
2007-08-08 16:22 ` [Patch 14/18] fs/logfs/progs/fsck.c Jörn Engel
2007-08-08 16:22 ` [Patch 15/18] fs/logfs/Locking Jörn Engel
2007-08-08 16:23 ` [Patch 16/18] fs/Kconfig Jörn Engel
2007-08-08 23:01 ` Arnd Bergmann
2007-08-09 20:03 ` Jörn Engel
2007-08-08 16:24 ` [Patch 17/18] fs/Makefile Jörn Engel
2007-08-08 16:24 ` [Patch 18/18] include/linux/Kbuild Jörn Engel
2007-08-09 0:19 ` Christoph Hellwig
2007-08-09 2:32 ` Jörn Engel
2007-08-09 2:39 ` Christoph Hellwig
2007-08-09 2:39 ` Jörn Engel
2007-08-09 2:45 ` Christoph Hellwig
2007-08-08 16:27 ` LogFS take five Artem Bityutskiy
2007-08-08 16:35 ` Jörn Engel
2007-08-08 16:52 ` Artem Bityutskiy [this message]
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=1186591920.19606.45.camel@sauron \
--to=dedekind@infradead.org \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.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