Subject: Re: LogFS take five
From: Artem Bityutskiy <dedekind@infradead.org>
Reply-To: dedekind@infradead.org
To: =?ISO-8859-1?Q?J=F6rn?= 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>
In-Reply-To: <20070808161234.GB15319@lazybastard.org>
References: <20070808161234.GB15319@lazybastard.org>
Content-Type: text/plain; charset=utf-8
Date: Wed, 08 Aug 2007 19:27:17 +0300
Message-Id: <1186590437.19606.38.camel@sauron>
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 877
Lines: 26

Hi Jörn,

On Wed, 2007-08-08 at 18:12 +0200, Jörn Engel wrote:
> It has been a while, mainly because I found a bunch of races and didn't
> want to publish anything before those were fixed.  Patch is still
> against 2.6.21 and just for review.

I'm very interested how do you account free/dirty space in LogFS:

* When you need to write new data, how do you select the place where to
write?
* When you run out of space, how do select find the segment to
garbage-collect?

For any given segment (or eraseblock), how do you find amount of free
and dirty space in it?

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/