mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lorenzo Allegrucci <l.allegrucci@tiscalinet.it>
To: "Theodore Ts'o" <tytso@mit.edu>,
	"Henning P. Schmiedehausen" <hps@intermeta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Add extended attributes to ext2/3
Date: Wed, 16 Oct 2002 19:50:54 +0200	[thread overview]
Message-ID: <200210161950.54993.l.allegrucci@tiscalinet.it> (raw)
In-Reply-To: <20021016161620.GC8210@think.thunk.org>

On Wednesday 16 October 2002 18:16, Theodore Ts'o wrote:
> On Wed, Oct 16, 2002 at 09:38:02AM +0000, Henning P. Schmiedehausen wrote:
> > tytso@mit.edu writes:
> > >+	int ea_blocks = EXT3_I(inode)->i_file_acl ?
> > >+		(inode->i_sb->s_blocksize >> 9) : 0;
> >
> > Sometimes I wonder if we shouldn't have the block size (512) and the
> > bit shift (9) as defines somewhere and gradually shift away from hard
> > coded values...
> >
> > If we ever decide to change the block size of ext2/ext3, we're in for
> > a "looking for nines"... :-)
>
> We already have different block sizes for ext2/3; we support 1k, 2k,
> and 4k block sizes.

BTW, why doesn't ext2/3 support 512 byte block sizes?


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 22:20 tytso
2002-10-16  9:38 ` Henning P. Schmiedehausen
2002-10-16 16:16   ` Theodore Ts'o
2002-10-16 17:05     ` Andreas Dilger
2002-10-16 19:30       ` Theodore Ts'o
2002-10-19 18:36         ` Jan Kara
2002-10-16 17:50     ` Lorenzo Allegrucci [this message]
2002-10-16 18:32       ` Andreas Dilger
     [not found] ` <200210161336.27935.agruen@suse.de>
     [not found]   ` <3DAD8D5E.31E177BA@digeo.com>
2002-10-16 20:32     ` [PATCH] linux-2.5.43-mm1: Further xattr/acl cleanups Andreas Gruenbacher
2002-10-16 21:15       ` Andreas Gruenbacher

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=200210161950.54993.l.allegrucci@tiscalinet.it \
    --to=l.allegrucci@tiscalinet.it \
    --cc=hps@intermeta.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 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®