From: Oleg Drokin <green@namesys.com>
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs blocks long on getdents64() during concurrent write
Date: Mon, 5 Aug 2002 09:44:29 +0400 [thread overview]
Message-ID: <20020805094429.A5897@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208041506480.31879-100000@pc40.e18.physik.tu-muenchen.de>
Hello!
On Sun, Aug 04, 2002 at 06:09:34PM +0200, Roland Kuhn wrote:
> The first call to getdents64 takes 4.7s! I captured the task status and
> got this:
[call traces skipped]
> writer is a shell script calling dd with a blocksize of 1M. The problem of
> course vanishes when using noatime, but it still makes me wonder why a
> single write request is delayed so long. The other possibility to avoid
It seems that your kernel performs writes slowly.
> this is to use a sync mount, and there I discovered something really
> strange: 2.4.19 gives me about 17MB/s while 2.4.18-3 (RedHat) was creeping
> slow with 10kB/s!
2.4.18-3 is particularly bad know for this exact problem (slow write speed),
you should consider upgrading to at least 2.4.18-5 kernel from redhat updates.
For me on plain 2.4.18 the problem is not visible that bad as for you.
I.e. ls on a directory where I write this big file finishes in under
half a second.
> If you have any thoughts on the cause of this behaviour and/or on how to
> fix it, I would be glad to hear them. If it's not too complicated I could
> even code something up myself, and I for sure can do any testing needed.
You said 2.4.19 writes stuff faster for you, how about testing ls on that
kernel?
Bye,
Oleg
next prev parent reply other threads:[~2002-08-05 5:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 16:09 reiserfs blocks long on getdents64() during concurrent write Roland Kuhn
2002-08-05 5:44 ` Oleg Drokin [this message]
2002-08-05 9:22 ` Roland Kuhn
2002-08-05 9:54 ` Oleg Drokin
2002-08-05 10:51 ` Roland Kuhn
2002-08-05 11:04 ` Oleg Drokin
2002-08-05 18:19 ` Roland Kuhn
2002-08-05 18:30 ` Oleg Drokin
2002-08-05 18:54 ` Chris Mason
2002-08-05 19:48 ` Roland Kuhn
2002-08-05 20:02 ` Roland Kuhn
2002-08-05 22:14 ` Chris Mason
2002-08-05 22:46 ` Roland Kuhn
2002-08-06 0:47 ` Chris Mason
2002-08-06 10:01 ` Roland Kuhn
2002-08-05 19:11 ` Roland Kuhn
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=20020805094429.A5897@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuhn@e18.physik.tu-muenchen.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