From: Andreas Dilger <adilger@clusterfs.com>
To: Alex Tomas <alex@clusterfs.com>
Cc: suparna@in.ibm.com, ext2-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [Ext2-devel] Re: Reviewing ext3 improvement patches (delalloc, mballoc, extents)
Date: Fri, 4 Mar 2005 11:25:33 -0700 [thread overview]
Message-ID: <20050304182533.GT27352@schnapps.adilger.int> (raw)
In-Reply-To: <20050304152946.5fb24686.alex@clusterfs.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Mar 04, 2005 15:29 +0300, Alex Tomas wrote:
> On Fri, 4 Mar 2005 16:43:31 +0530
> Suparna Bhattacharya <suparna@in.ibm.com> wrote:
>
> > Alex, have you had a chance to prototype your idea of rooting extents
> > in ea ?
>
> I think all you need for this are:
>
> 1) allocate EA in ext3_new_inode()
> 2) write a replacement for ext3_init_tree_desc()
> just few lines of code
> 3) write .get_write_access and .mark_buffer_dirty methods
> again few lines
> 4) use replacement of ext3_init_tree_desc() in few places
This should of course only be done for large inodes. Also, at some
point it will consume all of the EA space and we need to use an
external block. It might help in some middle cases (i.e. files with
more extents than can fit in i_blocks (60 bytes), but less than fit
into the large inode space (128 or maybe 384 bytes)) but it might
also hurt other things if we need to allocate an EA block for another
EA...
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-04 18:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 8:33 Reviewing ext3 improvement patches (delalloc, mballoc, extents) Suparna Bhattacharya
2005-03-03 9:40 ` Andreas Dilger
2005-03-03 22:10 ` Theodore Ts'o
2005-03-03 22:30 ` Alex Tomas
2005-03-04 11:13 ` Suparna Bhattacharya
2005-03-04 12:29 ` Alex Tomas
2005-03-04 18:25 ` Andreas Dilger [this message]
2005-03-04 1:12 ` [Ext2-devel] " Badari Pulavarty
2005-03-04 1:46 ` Mingming Cao
2005-03-04 3:26 ` Suparna Bhattacharya
2005-03-14 8:36 ` Werner Almesberger
2005-03-14 9:04 ` Suparna Bhattacharya
2005-03-14 15:02 ` Werner Almesberger
2005-03-14 15:43 ` Alex Tomas
2005-03-14 16:37 ` [Ext2-devel] " Werner Almesberger
2005-03-14 17:13 ` Alex Tomas
2005-03-15 0:28 ` Werner Almesberger
2005-03-14 22:23 ` Bryan Henderson
2005-03-15 0:42 ` Werner Almesberger
2005-03-15 21:59 ` Bryan Henderson
2005-03-04 11:30 ` [Ext2-devel] " Alex Tomas
2005-03-04 15:02 ` Alex Tomas
2005-03-13 14:41 ` Delayed alloc for ordered-mode Suparna Bhattacharya
2005-03-13 19:32 ` Badari Pulavarty
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=20050304182533.GT27352@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=alex@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=suparna@in.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).