linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: akpm@osdl.org, kiran@scalex86.org,
	Laurent Vivier <Laurent.Vivier@bull.net>,
	linux-kernel@vger.kernel.org,
	ext2-devel <ext2-devel@lists.sourceforge.net>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/3] ext3 percpu counter fixes to suppport for ext3 unsigned long type free blocks counter
Date: Tue, 11 Apr 2006 10:09:18 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0604111007230.564@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1144691929.3964.53.camel@dyn9047017067.beaverton.ibm.com>

On Mon, 10 Apr 2006, Mingming Cao wrote:

> Here are the proposed patches to allow the ext3 free block accounting
> works with more than 8TB storage.

Umm.. This is an issue on 32 bit platforms only. 64bit platforms x86_64, 
ia64 etc do not need this. Would you make it arch specific?

  reply	other threads:[~2006-04-11 17:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 17:58 [RFC][PATCH 0/3] ext3 percpu counter fixes to suppport for ext3 unsigned long type free blocks counter Mingming Cao
2006-04-11 17:09 ` Christoph Lameter [this message]
2006-04-11 19:01   ` Mingming Cao
2006-04-11 22:20     ` Ravikiran G Thirumalai
2006-04-12 21:28       ` [Ext2-devel] " Mingming Cao
2006-04-12 21:50         ` Andreas Dilger
2006-04-13 19:02         ` Ravikiran G Thirumalai
2006-04-13 22:25           ` Mingming Cao
2006-04-14  0:20             ` Ravikiran G Thirumalai
2006-04-21 14:59 ` [PATCH 1/2] ext3 percpu counter fixes to suppport for more than 2**31 ext3 " Mingming Cao
2006-04-21 22:09   ` Andrew Morton
2006-04-24 17:48     ` Mingming Cao
2006-04-24 18:26       ` Ravikiran G Thirumalai
2006-04-24 19:13         ` Mingming Cao
2006-04-22  0:56   ` Ravikiran G Thirumalai
2006-04-24 17:49     ` Mingming Cao
2006-04-24 22:51   ` [RESEND][PATCH 1/2] percpu counter data type changes " 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=Pine.LNX.4.64.0604111007230.564@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=Laurent.Vivier@bull.net \
    --cc=akpm@osdl.org \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=kiran@scalex86.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 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).