public inbox for linux-ia64@vger.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: Wed, 30 Jul 2003 18:51:33 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105959115622094@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105958015806246@msgid-missing>

On Wed, Jul 30, 2003 at 02:21:02PM -0400, Theodore Ts'o wrote:
> I'd be interested in benchmark runs comparing 4k, 8k, 16k, 32k, and
> 64k, if you would, please.  

vary kernel page size or ext2 block size or both together?
re-aim-7 benchmark or something different?
(and please don't say "dbench" :^)

32k is not possible in the kernel. Could use 64k.

Two of the re-aim-7 (aka osdl-aim-7) results (4k and 16k) are posted
on lkml and I can resend if I get a private request.

I'm going to be in transit or offline alot of the next 2 weeks.
Not likely I'll be able to generate the additional numbers.
Other volunteers?
I'm happy to share the s3kr3T osdl-aim-7 sauce recipe.

And I'd really just like to prove if VMERGE code in the BIO layer
is useful or not. I've concluded it's not useful for 53c1030.
I think it's more interesting to measure 53c1010.

> Was any patches necessary for the ia64 kernel before the block sizes >
> 8k started working for you?

nope. :^)
Just twiddle the CONFIG_IA64_PAGE_SIZE_* parameters if one wants 64KB.
16KB is the default.

thanks,
grant

  parent reply	other threads:[~2003-07-30 18:51 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 [this message]
2003-07-30 19:01 ` Grant Grundler
2003-07-30 21:15 ` Theodore Ts'o
2003-07-31  3:35 ` Grant Grundler
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-105959115622094@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox