From: Chris Mason <mason@suse.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.22pre6aa1
Date: 17 Jul 2003 20:30:16 -0400 [thread overview]
Message-ID: <1058488216.4016.338.camel@tiny.suse.com> (raw)
In-Reply-To: <20030717225002.GY1855@dualathlon.random>
On Thu, 2003-07-17 at 18:50, Andrea Arcangeli wrote:
> On Fri, Jul 18, 2003 at 12:30:45AM +0200, Marc-Christian Petersen wrote:
> > 2.4.22-pre[6|6aa1]:
> > -------------------
> > root@codeman:[/] # dd if=/dev/zero of=/home/largefile bs=16384 count=131072
> > 131072+0 records in
> > 131072+0 records out
> > 2147483648 bytes transferred in 128.765686 seconds (16677453 bytes/sec)
> >
> > 2.4.22-pre2:
> > ------------
> > root@codeman:[/] # dd if=/dev/zero of=/home/largefile bs=16384 count=131072
> > 131072+0 records in
> > 131072+0 records out
> > 2147483648 bytes transferred in 98.489331 seconds (21804226 bytes/sec)
> >
> > both kernels freshly rebooted.
>
> this explains it.
>
> Can you try to change include/linux/blkdev.h like this:
>
> -#define MAX_QUEUE_SECTORS (4 << (20 - 9)) /* 4 mbytes when full sized */
> +#define MAX_QUEUE_SECTORS (16 << (20 - 9)) /* 4 mbytes when full sized */
>
> This will raise the queue from 4 to 16M. That is the first(/only) thing
> that can explain a drop in performnace while doing contigous I/O.
> However I didn't expect it to make a difference, or at least not so
> relevant.
>
> If this doesn't help at all, it might not be an elevator/blkdev thing.
> At least on my machines the contigous I/O still at the same speed.
>
Especially with just one writer, you really shouldn't be able to see a
difference in pre6. Did you measure this change on both pre6 and
pre6aa1. Your message indicated that but I wanted to double check to
make sure.
-chris
next prev parent reply other threads:[~2003-07-18 0:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 10:28 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 10:42 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 10:52 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 10:53 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 15:42 ` 2.4.22pre6aa1 Dave Jones
2003-07-17 20:31 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:13 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:26 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:27 ` 2.4.22pre6aa1 Mike Fedyk
2003-07-17 22:32 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:30 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:50 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 0:30 ` Chris Mason [this message]
2003-07-22 12:28 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 14:04 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 5:47 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-22 13:34 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 13:59 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-24 12:27 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-24 14:14 ` 2.4.22pre6aa1 Chris Mason
2003-07-18 18:18 ` 2.4.22pre6aa1 Christoph Hellwig
2003-07-18 22:27 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 22:48 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 22:53 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:04 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 23:12 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:53 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-19 0:04 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-23 11:21 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 5:28 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-25 11:10 ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 19:02 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-03 17:12 ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-08-16 11:56 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-16 13:54 ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:00 ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:50 ` 2.4.22pre6aa1 Sergey S. Kostyliov
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=1058488216.4016.338.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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;
as well as URLs for NNTP newsgroup(s).