From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: Horrible ftruncate performance Date: Tue, 22 Jul 2003 22:09:28 +0400 Message-ID: <3F1D7DD8.3010806@namesys.com> References: <200307151848.59027.Dieter.Nuetzel@hamburg.de> <20030715170540.GA1213@namesys.com> <3F1D69AC.5040302@namesys.com> <1058892649.5042.29.camel@tiny.suse.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <1058892649.5042.29.camel@tiny.suse.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Chris Mason Cc: Oleg Drokin , Dieter N?tzel , Szakacsits Szabolcs , Carl-Daniel Hailfinger , reiserfs-list@namesys.com Chris Mason wrote: >On Tue, 2003-07-22 at 12:43, Hans Reiser wrote: > > >>The answer to the below is to use reiser4. It uses extents, and two 64 >>bit numbers are all that is needed to store the hole. V4 will be ready >>for testing in a few days, and will ship for real users at the end of >>summer we hope. >> >>Fixing V3 is the wrong answer: this is one of its design flaws. >> >> > >It's important to remember that releasing v4 doesn't automatically >convert all existing v3 users to it. This is the kind of thing we >should try to fix without making major design changes to v3. It's at >least worth talking about, "use v4" can't always be the answer. > V3 is in feature freeze. Unfortunately, determining what is a feature and what is a bug is a process based not just on the user experience, but on the structure of the code. The proper fix for this bug is to add a feature called extents. This belongs in, and is in, V4. V4 will be available very soon. Adding features, like new kinds of items, will disturb the stability of V3. V3 needs to be zero defect. It is now in a phase in its lifetime where conservatism is appropriate. > >-chris > > > > > > -- Hans