From: Mingming Cao <cmm@us.ibm.com>
To: ext2-devel <ext2-devel@lists.sourceforge.net>
Cc: Andrew Morton <akpm@osdl.org>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Badari Pulavarty <pbadari@us.ibm.com>,
suparna@in.ibm.com, tytso@mit.edu, alex@clusterfs.com,
adilger@clusterfs.com
Subject: Re: [RFC] [PATCH 0/4]Multiple block allocation and delayed allocation for ext3
Date: Sun, 17 Jul 2005 10:45:38 -0700 [thread overview]
Message-ID: <1121622338.4609.32.camel@localhost.localdomain> (raw)
In-Reply-To: <1121622002.4609.23.camel@localhost.localdomain>
On Sun, 2005-07-17 at 10:40 -0700, Mingming Cao wrote:
> Hi All,
>
> Here are the updated patches to support multiple block allocation and
> delayed allocation for ext3 done by me, Badari and Suparna.
Patches are against 2.6.13-rc3.
Mingming
WARNING: multiple messages have this Message-ID (diff)
From: Mingming Cao <cmm@us.ibm.com>
To: ext2-devel <ext2-devel@lists.sourceforge.net>
Cc: Andrew Morton <akpm@osdl.org>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Badari Pulavarty <pbadari@us.ibm.com>,
suparna@in.ibm.com, tytso@mit.edu, alex@clusterfs.com,
adilger@clusterfs.com
Subject: Re: [RFC] [PATCH 0/4]Multiple block allocation and delayed allocation for ext3
Date: Sun, 17 Jul 2005 10:45:38 -0700 [thread overview]
Message-ID: <1121622338.4609.32.camel@localhost.localdomain> (raw)
In-Reply-To: <1121622002.4609.23.camel@localhost.localdomain>
On Sun, 2005-07-17 at 10:40 -0700, Mingming Cao wrote:
> Hi All,
>
> Here are the updated patches to support multiple block allocation and
> delayed allocation for ext3 done by me, Badari and Suparna.
Patches are against 2.6.13-rc3.
Mingming
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-17 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1110839154.24286.302.camel@dyn318077bld.beaverton.ibm.com>
2005-07-17 17:40 ` [RFC] [PATCH 0/4]Multiple block allocation and delayed allocation for ext3 Mingming Cao
2005-07-17 17:45 ` Mingming Cao [this message]
2005-07-17 17:45 ` Mingming Cao
2005-07-17 17:40 ` [RFC] [PATCH 1/4]Multiple block " Mingming Cao
2005-07-17 17:40 ` Mingming Cao
2005-07-17 17:40 ` [RFC] [PATCH 2/4]delayed " Mingming Cao
2005-07-18 1:47 ` [Ext2-devel] " Andreas Dilger
2005-07-18 17:32 ` Mingming Cao
2005-07-19 0:25 ` Badari Pulavarty
2005-07-26 22:52 ` Andrew Morton
2005-07-26 22:52 ` Andrew Morton
2005-07-26 22:55 ` Badari Pulavarty
2005-07-26 22:55 ` Badari Pulavarty
2005-07-17 17:40 ` [RFC] [PATCH 3/4]generic getblocks() support in mpage_writepages Mingming Cao
2005-07-17 17:40 ` Mingming Cao
2005-07-17 17:41 ` [RFC] [PATCH 4/4]add ext3 writeback writpages Mingming Cao
2005-07-17 17:41 ` Mingming Cao
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=1121622338.4609.32.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=alex@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=sct@redhat.com \
--cc=suparna@in.ibm.com \
--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 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.