From: Alex Tomas <alex@clusterfs.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Mingming Cao <cmm@us.ibm.com>, coly <colyli@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: where is the ext4 git tree ?
Date: Fri, 26 Jan 2007 13:47:24 -0700 [thread overview]
Message-ID: <20070126204724.GA14191@mail.clusterfs.com> (raw)
In-Reply-To: <20070126165119.GC14759@thunk.org>
On Fri, Jan 26, 2007 at 11:51:19AM -0500, Theodore Tso wrote:
> The first patch series can be found here:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/2.6.20-rc5-ext4-1
>
> I've included Alex's latest patches which he sent back in December,
> but I haven't gone back before that looking for patches from before.
> If you think there is a patch which should be included that hasn't
> been, please repost it to linux-ext4.
I'd appreciate a lot review and discussion of mballoc's design.
the most serious change over the last version is preallocation. because
of specific workloads our customers like we have to support multiple
preallocations per inode.
a bit about structures ... every preallocated chunk is described with a
special structure. preallocated space is assigned to logical offset of
a file. the structure is on two lists:
1) preallocations in a group
2) preallocations in an inode
before searching blocks, mballoc loads on-disk bitmap and generates:
1) in-core bitmap, which is copy of on-disk bitmap + all preallocated
blocks in the group
2) buddy, which is generated from in-core bitmap
once the both structures are initialized, mballoc finds suitable space
and creates preallocation descriptor, if preallocation is requested.
subsquent allocations find the descriptor via per-inode list using logical
offset as a key and mark block(s) used in on-disk bitmap.
thanks, Alex
next prev parent reply other threads:[~2007-01-26 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 10:05 where is the ext4 git tree ? coly
2007-01-26 15:56 ` Mingming Cao
2007-01-26 16:04 ` coly
2007-01-26 16:51 ` Theodore Tso
2007-01-26 20:47 ` Alex Tomas [this message]
2007-01-27 13:26 ` coly
2007-01-27 21:53 ` Theodore Tso
2007-01-28 5:09 ` coly
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=20070126204724.GA14191@mail.clusterfs.com \
--to=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=colyli@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).