From: Oleg Drokin <green@namesys.com>
To: wolfgang.glas@ev-i.at
Cc: reiserfs-list@namesys.com
Subject: Re: kernel loop with lseek + LFS on reiser partition.
Date: Mon, 22 Apr 2002 16:10:07 +0400 [thread overview]
Message-ID: <20020422161007.A885@namesys.com> (raw)
In-Reply-To: <OF6E1F14ED.2ACEFBDE-ONC1256BA3.003EF743@ev-i.at>
Hello!
On Mon, Apr 22, 2002 at 01:30:58PM +0200, wolfgang.glas@ev-i.at wrote:
> OK, The program terminates.
Good.
> Seems to scale linear with CPU power......
As expected. I am experimenting in 2 directions currently:
One is to speed up the lenghtly operation itself ( got cpu time spent down
to 8 seconds already, but some problems still persists).
Another one is to simply allow for this process to be terminated.
Bye,
Oleg
next prev parent reply other threads:[~2002-04-22 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 11:30 kernel loop with lseek + LFS on reiser partition wolfgang.glas
2002-04-22 12:10 ` Oleg Drokin [this message]
[not found] <200204221910.16392.Dieter.Nuetzel@hamburg.de>
2002-04-23 4:58 ` 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=20020422161007.A885@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--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.