From: Oleg Drokin <green@namesys.com>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: wolfgang.glas@ev-i.at, Chris Mason <mason@suse.com>,
Robert Love <rml@tech9.net>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: kernel loop with lseek + LFS on reiser partition.
Date: Tue, 23 Apr 2002 08:58:00 +0400 [thread overview]
Message-ID: <20020423085800.B4770@namesys.com> (raw)
In-Reply-To: <200204221910.16392.Dieter.Nuetzel@hamburg.de>
Hello!
On Mon, Apr 22, 2002 at 07:10:16PM +0200, Dieter N?tzel wrote:
> > I think this is because of expanding-truncate patch.
> > So, the real bug is this process cannot get interrupted until finished
> > which opens a window for resource-eating.
> /database/db1> time ~/Entwicklung/ReiserFS/testprg
> 0.000u 545.310s 9:12.69 98.6% 0+0k 0+0io 124pf+0w
9 minutes as expected from your HW config.
> -rw-r--r-- 1 nuetzel users 137438953485 Apr 22 17:22 seek.tmp
> /dev/sdb5 859412 166264 693148 20% /database/db1
> Isn't this only a "bad" glibc "speed test"?
Huh? glibc have nothing to do with this result.
> With my latest latencytest0.42-png tests I found that there are one or two
> locks remaining in the VFS or ReiserFS code (preemption and/or lock-break
> could be the culprit, too).
We already have identified a problem place and testing the patch before
releasing it to the public.
Bye,
Oleg
next parent reply other threads:[~2002-04-23 4:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204221910.16392.Dieter.Nuetzel@hamburg.de>
2002-04-23 4:58 ` Oleg Drokin [this message]
2002-04-22 11:30 kernel loop with lseek + LFS on reiser partition wolfgang.glas
2002-04-22 12:10 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 9:49 wolfgang.glas
2002-04-22 10:02 ` Oleg Drokin
2002-04-22 8:28 wolfgang.glas
2002-04-22 8:32 ` Oleg Drokin
2002-04-22 9:35 ` Oleg Drokin
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=20020423085800.B4770@namesys.com \
--to=green@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=rml@tech9.net \
--cc=wolfgang.glas@ev-i.at \
/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.