All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Add extended attributes to ext2/3
Date: Tue, 15 Oct 2002 17:52:58 -0700	[thread overview]
Message-ID: <3DACB86A.829ECF3C@digeo.com> (raw)
In-Reply-To: 200210160211.39284.agruen@suse.de

Andreas Gruenbacher wrote:
> 
> ..
> > This should be converted to use sector_t for >2TB support, and tested
> > with CONFIG_LBD=y and n.
> 
> e_block is the block number; the e_indexes are hash values. Ext[23] only has
> 32bit block numbers. Am I getting you wrong?

Well it depends how generic the mbcache code is supposed to be.

The kernel has just gained supoprt for 64-bit sectors on ia32
and PPC32 but the new mbcache code will not support that.

I guess if there are no current 64-bit users of mbcache then
it can be deferred until there is a need.

> > The use of a dev_t search key is a bit old-fashioned.  Maybe
> > use the address of inode->i_sb->s_bdev?
> 
> That would do as well.
> 
> A related issue:
> 
> Would switching to a more decent hash algorithm in fs/ext?/xattr.c make sense?
> I think there are better ones in 2.5. This would only degrade sharing on
> "legacy" systems for a while, but the slow down would vanish over time.

Might do.  There's hash_long() in <linux/hash.h>

  reply	other threads:[~2002-10-16  0:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 22:20 [PATCH 1/3] Add extended attributes to ext2/3 tytso
2002-10-16  0:00 ` Andrew Morton
2002-10-16  0:11   ` Andreas Gruenbacher
2002-10-16  0:52     ` Andrew Morton [this message]
2002-10-16  1:20       ` Andi Kleen
2002-10-16  1:43         ` David S. Miller
2002-10-16 16:04   ` Theodore Ts'o
     [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=3DACB86A.829ECF3C@digeo.com \
    --to=akpm@digeo.com \
    --cc=agruen@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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.