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
