From: Hans Reiser <reiser@namesys.com>
To: ReiserFS List <reiserfs-list@namesys.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: reiser4 for 2.6.13 is available on our website
Date: Thu, 29 Sep 2005 10:25:54 -0700 [thread overview]
Message-ID: <433C23A2.9020403@namesys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
Reiser4 performance dropped in the -mm series due to the write
throttling patch and also dropped due to a fixed bug (removing type safe
lists added a bug). We don't yet know if we got quite all the
performance back, we are still testing. Conservative users should wait
a week or two to see if bug reports with reiser4 remain, or if indeed we
did get all the bugs out of the recent cleanup patch.
Hans
[-- Attachment #2: vs's dayly report for september, 2005 (thebsh refuses ssh access) --]
[-- Type: message/rfc822, Size: 1173 bytes --]
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Subject: vs's dayly report for september, 2005 (thebsh refuses ssh access)
Date: Thu, 29 Sep 2005 19:11:15 +0400
Message-ID: <433C0413.6080002@namesys.com>
BEG 2005.09.29:10.21 Thu
END 2005.09.29:14.11 Thu TOTAL=3:50
BEG 2005.09.29:14.40 Thu
CHATS: preparing reiser4 patches for 2.6.13
making sure that per-task-predictive-write-throttling-1.patch is
responsible
for reiser4 performance drop in 2.6.14-rcX-mmY
at least it is responsible for substantial part of it
END 2005.09.29:19.09 Thu TOTAL=4:29
next reply other threads:[~2005-09-29 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 17:25 Hans Reiser [this message]
2005-09-29 18:24 ` reiser4 for 2.6.13 is available on our website Łukasz Mierzwa
2005-09-29 22:09 ` Jake Maciejewski
2005-09-29 22:32 ` Hans Reiser
2005-09-29 23:23 ` Gregory Maxwell
2005-09-30 2:59 ` Dan Oglesby
2005-09-30 3:03 ` Dan Oglesby
2005-09-30 5:02 ` Dan Oglesby
2005-09-30 6:01 ` Dan Oglesby
2005-09-30 8:31 ` Alexander Zarochentsev
2005-09-30 12:01 ` Łukasz Mierzwa
2005-10-01 7:20 ` Jake Maciejewski
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=433C23A2.9020403@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--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.