mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Alex Tomas <bzzz@tmi.comex.ru>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [RFC] fast EA for ext3
Date: Sun, 18 May 2003 16:57:18 -0600	[thread overview]
Message-ID: <20030518165718.B11651@schatzie.adilger.int> (raw)
In-Reply-To: <87n0hkmbiw.fsf@gw.home.net>; from bzzz@tmi.comex.ru on Sun, May 18, 2003 at 05:04:39PM +0000

On May 18, 2003  17:04 +0000, Alex Tomas wrote:
> this patch implements possibility to store EA into inode body
> which may be larger 128 bytes in 2.5 kernel.

What Alex didn't mention was the reason why we developed this patch in the
first place - speed.  Storing EAs in external blocks is slow, and if you
have a lot of inodes with external EAs it is fatal, as the EA blocks consume
so much RAM that they force all of the inode/directory data out of cache.


Some benchmarks (from Alex):
> environment for  old EA: just mkfs'ed EXT3, inode size 128, 33000 files
> environment for fast EA: just mkfs'ed EXT3, inode size 256, 33000 files
> 
>                      old EA       fast EA
> add attributes       2m35.241s    1m4.151s   (+142%)
> dump attributes      0m28.716s    0m13.466s  (+113%)
> change attributes    2m42.108s    1m4.413s   (+153%)
> remove attributes    1m15.373s    1m3.909s   (+19%)

Some minor improvements could be made, such as not storing user EAs inside
the inode if there are system EAs that could be stored there.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2003-05-18 22:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 17:04 Alex Tomas
2003-05-18 22:57 ` Andreas Dilger [this message]
2003-05-21 23:33   ` [Ext2-devel] " Andreas Gruenbacher
2003-05-22  4:16     ` Andreas Dilger

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=20030518165718.B11651@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --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

all inboxes | Powered by JetHome®