All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: EXT2_MAX_BLOCK_LOG_SIZE increase?
Date: Thu, 31 Jul 2003 03:35:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105962255218555@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105958015806246@msgid-missing>

On Wed, Jul 30, 2003 at 05:15:33PM -0400, Theodore Ts'o wrote:
> Well, varying both, actually.  I'm curious whether it is a large block
> size, or block_size = page_size that really matters.

sorry - I'm not sure I understand the distinction.
My take is a larger page size (ie 16k is better than 4k).
It looks like ext2 uses PAGE_SIZE to size it's IOs:

> The reason why I care is because it makes a difference as to what the
> default mke2fs hueristics should be.

My gut feeling is native page_size and then warn about compatibility
if that is > 4k.

> (By the way, even without
> hacking e2fsprogs at all, if you use mke2fs -Tlargefile, it will use a
> default blocksize = pagesize, and this currently bypasses the
> EXT2_MAX_BLOCK_SIZE check entirely.)  The question is whether or not
> this is really optimal behaviour....

re-aim-7 seems to think so.
I sent you privately the 4k and 16k pagesize runs that I had posted earlier.

grant

  parent reply	other threads:[~2003-07-31  3:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 15:38 EXT2_MAX_BLOCK_LOG_SIZE increase? Grant Grundler
2003-07-30 18:21 ` Theodore Ts'o
2003-07-30 18:51 ` Grant Grundler
2003-07-30 19:01 ` Grant Grundler
2003-07-30 21:15 ` Theodore Ts'o
2003-07-31  3:35 ` Grant Grundler [this message]
2003-07-31  4:00 ` Grant Grundler

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=marc-linux-ia64-105962255218555@msgid-missing \
    --to=iod00d@hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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.