From: Hans Reiser <reiser@namesys.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: Pysiak Satriani <pysiak.satriani@wp.pl>, reiserfs-list@namesys.com
Subject: Re: Reiser4 O_DIRECT
Date: Sun, 22 May 2005 10:31:19 -0700 [thread overview]
Message-ID: <4290C1E7.9050505@namesys.com> (raw)
In-Reply-To: <20050522171207.GB11013@nysv.org>
Markus Törnqvist wrote:
>On Sun, May 22, 2005 at 12:43:52AM -0700, Hans Reiser wrote:
>
>
>>What Vladimir failed to say was that it is our recent changes to
>>accomodate the kernel maintainers that are unstable, we had previously
>>reached the point where none of our internal tests could make it crash.
>>I hope that he did not put these unstable changes on our website for
>>users to see them without special notes....
>>
>>
>
>This is probably still true for performance as well, yes?
>
>I haven't been testing Reiser4 for too long, I just set up a 32-bit
>chroot and chose Reiser4 for it so I may be able to resume my
>freelance-toying with it. If I can arrange more spare time.
>
>Any suggestions for performance/latency benchmark suites, preferrably
>automated, are welcome, of course ;)
>
>
>
Something is currently making our performance erratic for multiple
streams of IO.
next prev parent reply other threads:[~2005-05-22 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 17:53 Reiser4 O_DIRECT Martin Piayda
2005-05-20 8:42 ` Vladimir Saveliev
2005-05-21 21:49 ` Re[2]: " Pysiak Satriani
2005-05-22 7:43 ` Hans Reiser
2005-05-22 17:12 ` mjt
2005-05-22 17:31 ` Hans Reiser [this message]
2005-05-22 17:38 ` Martin Piayda
2005-05-26 19:25 ` evilninja
2005-05-22 22:47 ` Re[2]: " Valdis.Kletnieks
2005-05-23 0:22 ` David Masover
2005-05-23 1:04 ` Valdis.Kletnieks
2005-05-23 9:52 ` mjt
2005-05-23 16:53 ` Valdis.Kletnieks
2005-05-23 17:53 ` Hans Reiser
2005-05-24 21:35 ` David Masover
2005-05-24 21:55 ` Valdis.Kletnieks
2005-05-24 23:28 ` David Masover
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=4290C1E7.9050505@namesys.com \
--to=reiser@namesys.com \
--cc=mjt@nysv.org \
--cc=pysiak.satriani@wp.pl \
--cc=reiserfs-list@namesys.com \
/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.