All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: tytso@valinux.com
Cc: Alexander Viro <viro@math.psu.edu>,
	linux-kernel@vger.kernel.org,
	Andreas Dilger <adilger@turbolinux.com>,
	Ext2 development mailing list  <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] ext2 inode size (on-disk)
Date: Thu, 19 Apr 2001 16:29:52 -0400	[thread overview]
Message-ID: <3ADF4AC0.2485C0BC@mandrakesoft.com> (raw)
In-Reply-To: <20001202014045.F2272@parcelfarce.linux.theplanet.co.uk> <Pine.GSO.4.21.0104190719240.16930-100000@weyl.math.psu.edu> <20010419161003.E17837@snap.thunk.org>

tytso@valinux.com wrote:
> In the long run, it probably makes sense to adjust the algorithms to
> allow for non-power-of-two inode sizes,

If you don't mind, does that imply packing inodes across block
boundaries?

Regards,

	Jeff


-- 
Jeff Garzik       | "The universe is like a safe to which there is a
Building 1024     |  combination -- but the combination is locked up
MandrakeSoft      |  in the safe."    -- Peter DeVries

  reply	other threads:[~2001-04-19 20:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001202014045.F2272@parcelfarce.linux.theplanet.co.uk>
2001-04-19 11:55 ` ext2 inode size (on-disk) Alexander Viro
2001-04-19 17:41   ` Andreas Dilger
2001-04-19 18:02     ` Alexander Viro
2001-04-19 19:24       ` Andreas Dilger
2001-04-20  2:12         ` Alexander Viro
2001-04-19 20:10   ` [Ext2-devel] " tytso
2001-04-19 20:29     ` Jeff Garzik [this message]
2001-04-20  6:30       ` Theodore Tso
2001-04-20  2:23     ` Alexander Viro
2001-04-20  5:35       ` Andreas Dilger
2001-04-20  6:37         ` Theodore Tso
2001-04-20  6:35       ` Theodore Tso

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=3ADF4AC0.2485C0BC@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=adilger@turbolinux.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@valinux.com \
    --cc=viro@math.psu.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.