From: Mingming Cao <cmm@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Takashi Sato <sho@tnes.nec.co.jp>, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 0/4] 64k pagesize/blocksize fixes
Date: Wed, 26 Sep 2007 10:58:34 -0700 [thread overview]
Message-ID: <1190829514.4517.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20070925233049.656803267@sgi.com>
On Tue, 2007-09-25 at 16:30 -0700, Christoph Lameter wrote:
> Attached the fixes necessary to support 64k pagesize/blocksize. I think these are useful
> independent of the large blocksize patchset since there are architectures that support
> 64k page size and that could use these large buffer sizes without the large buffersize
> patchset.
>
> Are these patches in the right shape to be merged? I rediffed these against 2.6.32-rc8-mm1.
>
> I had to fix some things in the second patch (ext2) that may need some review since the
> way that commits work changed.
>
Thanks, As Andreas mentioned in another email there is a better way to
deal with rec_len issue on 64k block size. I will get those patches
merged in ext4 patch queue. I think the updated patches could get
merged.
Mingming
prev parent reply other threads:[~2007-09-26 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 23:30 [patch 0/4] 64k pagesize/blocksize fixes Christoph Lameter
2007-09-25 23:30 ` [patch 1/4] Increase limits for 64k page size support for Ext2/3/4 Christoph Lameter
2007-09-25 23:30 ` [patch 2/4] ext2: fix rec_len overflow for 64KB block size Christoph Lameter
2007-09-26 0:42 ` Andreas Dilger
2007-09-26 17:27 ` Christoph Lameter
2007-09-25 23:30 ` [patch 3/4] ext3: fix rec_len overflow with " Christoph Lameter
2007-09-25 23:30 ` [patch 4/4] ext4: fix rec_len overflow for " Christoph Lameter
2007-09-26 17:58 ` Mingming Cao [this message]
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=1190829514.4517.7.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
/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).