public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ramón Rey Vicente󮠒" <retes_simbad@yahoo.es>
To: Alex Tomas <bzzz@tmi.comex.ru>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	ext2-devel@lists.sourceforge.net
Subject: Re: [RFC] extents support for EXT3
Date: Fri, 29 Aug 2003 00:00:45 +0200	[thread overview]
Message-ID: <1062086590.2623.3.camel@debian> (raw)
In-Reply-To: <m33cfm19ar.fsf@bzzz.home.net>

El jue, 28-08-2003 a las 10:22, Alex Tomas escribió:

> this is 2nd version of the patch. changes:
>   - error handling seems completed
>   - lots of cleanups and comments
>   - few minor bug fixed
> 
> this version of the patch tries to solve couple
> of corner cases:
>   - very long truncate
>   - rewrite 
> 
> it survived dbench, bonnie++ and fsx tests.

It seems very good job.

> take a look at numbers I've just got, please.
> 
>                       before      after
> 5GB file, creation:   2m31.197s   2m21.933s
> 5GB file, read:       2m25.439s   2m24.833s
> 5GB file, rewrite:    2m48.434s   2m20.958s
> 5GB file, removal:    0m8.760s    0m0.858s
> 
>              before           after
> dbench 16:   99.9868 MB/sec   179.243 MB/sec 16 procs
> dbench 16:   89.9919 MB/sec   203.119 MB/sec 16 procs
> dbench 16:   73.5519 MB/sec   185.815 MB/sec 16 procs
> dbench 16:   94.6312 MB/sec   188.519 MB/sec 16 procs
> 
> 
> to use extents you have to use 'extents' mount option

This patch could be included with ext3 in 2.6.x?
-- 
Ramón Rey Vicente       <ramon dot rey at hispalinux dot es>
        jabber ID       <rreylinux at jabber dot org>
------------------------------------------------------------
gpg public key ID 0xBEBD71D5 # http://pgp.escomposlinux.org/


  parent reply	other threads:[~2003-08-28 22:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28  8:22 [RFC] extents support for EXT3 Alex Tomas
2003-08-28 17:22 ` [Ext2-devel] " Mike Fedyk
2003-08-29  5:55   ` Alex Tomas
2003-08-28 18:12 ` Ed Sweetman
2003-08-29  5:59   ` Alex Tomas
2003-08-29 15:28     ` Ed Sweetman
2003-08-29 15:38       ` Alex Tomas
2003-08-29 15:52         ` Ed Sweetman
2003-08-29 16:10           ` Alex Tomas
2003-08-29 16:16             ` Alex Tomas
2003-08-29 16:20             ` Ed Sweetman
2003-08-29 16:34               ` Alex Tomas
2003-08-29 17:49                 ` Ed Sweetman
2003-08-29 18:09                   ` Alex Tomas
2003-08-29 19:55                     ` Ed Sweetman
2003-08-29 21:39                       ` [Ext2-devel] " Mike Fedyk
2003-08-29 22:25                         ` Ed Sweetman
2003-08-29 23:17                           ` Mike Fedyk
2003-08-31 20:25                             ` Eric W. Biederman
2003-08-31 20:37                               ` Alex Tomas
2003-09-05 10:06                               ` Pavel Machek
2003-09-05 14:55                                 ` Eric W. Biederman
2003-08-30  9:09                       ` Alex Tomas
2003-08-30  8:55                   ` Alex Tomas
2003-08-30 10:13                   ` Alex Tomas
2003-08-28 22:00 ` Ramón Rey Vicente󮠒 [this message]
2003-08-29  6:04   ` Alex Tomas
2003-08-29  9:55     ` Ramón Rey Vicente󮠒
2003-09-06  0:19 ` jw schultz
2003-09-06  6:09   ` Alex Tomas

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=1062086590.2623.3.camel@debian \
    --to=retes_simbad@yahoo.es \
    --cc=bzzz@tmi.comex.ru \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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