All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Lorenzo Allegrucci <l.allegrucci@tiscalinet.it>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	"Henning P. Schmiedehausen" <hps@intermeta.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Add extended attributes to ext2/3
Date: Wed, 16 Oct 2002 12:32:55 -0600	[thread overview]
Message-ID: <20021016183255.GB1201@clusterfs.com> (raw)
In-Reply-To: <200210161950.54993.l.allegrucci@tiscalinet.it>

On Oct 16, 2002  19:50 +0200, Lorenzo Allegrucci wrote:
> On Wednesday 16 October 2002 18:16, Theodore Ts'o wrote:
> > 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?

Too inefficient, and impose too many limitations on the filesystem
(which sets up some filesystem structures based on the blocksize).
Already, 1kB block size is too small for many things, and 4kB is
preferred.  It would probably support larger blocksizes already on
ia32 if the page size was larger.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-10-16 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 22:20 [PATCH 2/3] Add extended attributes to ext2/3 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
2002-10-16 18:32       ` Andreas Dilger [this message]
     [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=20021016183255.GB1201@clusterfs.com \
    --to=adilger@clusterfs.com \
    --cc=hps@intermeta.de \
    --cc=l.allegrucci@tiscalinet.it \
    --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.