linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/9] 48-bit block numbers for extended attributes
Date: Thu, 10 Aug 2006 10:27:31 -0700	[thread overview]
Message-ID: <44DB6C83.5030402@us.ibm.com> (raw)
In-Reply-To: <20060809234100.9337162d.akpm@osdl.org>

Andrew Morton wrote:

> On Wed, 09 Aug 2006 18:22:09 -0700
> Mingming Cao <cmm@us.ibm.com> wrote:
> 
> 
>>As we are planning to support 48-bit block numbers for ext4,
>>we need to support 48-bit block numbers for extended attributes.
>>In the short term, we can do this by reuse (on-disk) 16-bit
>>padding (linux2.i_pad1 currently used only by "hurd") as high 
>>order bits for xattr. This patch basically does that.
> 
> 
> Short-term tends to become medium-term, then you're stuck with it.
> 
> What is the plan here?

At the time we discuss how to support 48 bit xattr in the current inode, 
we were thinking about patching ext3, thus it's not likely we will going 
to do a deep surgery on the on-disk ext3 inode itself to have room for 
another 16bit xattr. So the plan at that is to steal some unused bits 
and construct with existing 32bit xattr to come with a 48bit xattr in total.

Given the fact that we are creating a new filesystem ext4, the ideal way 
(long term) probably we should support 64bit xattr in the ext4 inode, 
that is possible. The plan is to focus on support 48bit ext4 first, then 
probably move on next few things that also requires on-disk format 
changes, this is an experiment filesystem at this moment....

Thanks,
Mingming


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-08-10 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:22 [PATCH 8/9] 48-bit block numbers for extended attributes Mingming Cao
2006-08-10  6:41 ` Andrew Morton
2006-08-10 17:27   ` 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=44DB6C83.5030402@us.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --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).