From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: linux-ext4@vger.kernel.org
Subject: Re: [RFC] mballoc patches
Date: Mon, 13 Aug 2007 22:08:26 +0530 [thread overview]
Message-ID: <46C08902.7020709@linux.vnet.ibm.com> (raw)
In-Reply-To: <1187000545401-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Aneesh Kumar K.V wrote:
> Alex actually pointed me the new mballoc patches at
> ftp://ftp.clusterfs.com/pub/people/alex/mballoc3
>
> The series is the forward port of the same on top of
> d4ac2477fad0f2680e84ec12e387ce67682c5c13 (v2.6.23-rc2)
>
>
> I guess the mballoc3 patch at clusterfs.com is based on
> a patched ext3(I guess it is ext3 + extent tree local to
> clusterfs ? ). The following series is based on ext4.
>
>
> I tested the changes with different blocks per group
> combination and it seems to be working fine. (The last
> series did panic with mke2fs -g 800 )
>
>
> I will now look at splitting this to smaller patches.
>
> NOTE : I am not sure whether patch 2 will be able to make the list.
> if not is there a place i can ftp/scp them so that others can access
> the same ?
>
>
I am attaching below the PATCH 2/4 in .gz format. The uncompressed one
got dropped by the list.
-aneesh
[-- Attachment #2: 0002-mballoc-core-patch.patch.gz --]
[-- Type: application/x-gzip, Size: 31201 bytes --]
next prev parent reply other threads:[~2007-08-13 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 10:22 [RFC] mballoc patches Aneesh Kumar K.V
2007-08-13 10:22 ` [PATCH 1/4] Add some new function for searching extent tree Aneesh Kumar K.V
[not found] ` <1187000553923-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
2007-08-13 10:22 ` [PATCH 3/4] This is the equivalent of ext3-mballoc3-sles10.patch Aneesh Kumar K.V
2007-08-13 10:22 ` [PATCH 4/4] Fixes to make it build and run Aneesh Kumar K.V
2007-08-13 16:38 ` Aneesh Kumar K.V [this message]
2007-08-21 21:00 ` [RFC] mballoc patches Eric Sandeen
2007-09-10 12:29 ` Alex Tomas
2007-09-10 14:35 ` Eric Sandeen
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=46C08902.7020709@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.