mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Andrew Morton <akpm@digeo.com>
Cc: Andreas Gruenbacher <agruen@suse.de>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Add extended attributes to ext2/3
Date: Wed, 16 Oct 2002 12:04:08 -0400	[thread overview]
Message-ID: <20021016160408.GB8210@think.thunk.org> (raw)
In-Reply-To: <3DACAC0C.D4C497C1@digeo.com>

On Tue, Oct 15, 2002 at 05:00:12PM -0700, Andrew Morton wrote:
> 
> This should be converted to use sector_t for >2TB support, and tested
> with CONFIG_LBD=y and n.
> 

It's only used to store an ext2/3 block number (not a 512 byte sector
number, but a 1k, 2k, or 4k fs block number).  

Changing it to be sector_t wouldn't hurt, but it would be less
efficient if CONFIG_LBD were turned on, since ext2/3 would only store
32 bit values into it.  If someone needed it for the future, the
change could take place then.  It's a simple change: change the type
of e_block, in mbcache.h, and the type of "block" in the function
parameters of mb_cache_entry_insert and mb_cache_entry_get, and you're
done.  No change would be needed in the ext3 code.

> The use of a dev_t search key is a bit old-fashioned.  Maybe
> use the address of inode->i_sb->s_bdev?

Sure, that would be easy enough to do.  In the next patch....

						- Ted

  parent reply	other threads:[~2002-10-16 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 22:20 tytso
2002-10-16  0:00 ` Andrew Morton
2002-10-16  0:11   ` Andreas Gruenbacher
2002-10-16  0:52     ` Andrew Morton
2002-10-16  1:20       ` Andi Kleen
2002-10-16  1:43         ` David S. Miller
2002-10-16 16:04   ` Theodore Ts'o [this message]
     [not found] <698528293@toto.iv>
     [not found] ` <15788.54887.251518.350350@wombat.chubb.wattle.id.au>
2002-10-16 14:01   ` Andi Kleen

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=20021016160408.GB8210@think.thunk.org \
    --to=tytso@mit.edu \
    --cc=agruen@suse.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®