From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Alexey Polyakov <alexey.polyakov@gmail.com>,
Hans Reiser <reiser@namesys.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>,
Nate Diller <ndiller@namesys.com>
Subject: Re: [PATCH] updated reiser4 - reduced cpu usage for writes by writing more than 4k at a time (has implications for generic write code and eventually for the IO layer)
Date: Thu, 08 Jun 2006 16:40:40 +0400 [thread overview]
Message-ID: <1149770440.6336.39.camel@tribesman.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0606081245160.28703@yvahk01.tjqt.qr>
Hello
On Thu, 2006-06-08 at 12:45 +0200, Jan Engelhardt wrote:
> >> > I'm actively using Reiser4 on a production servers (and I know a lot
> >> > of people that do that too).
> >> > Could you please release the patch against the vanilla tree?
> >> > I don't think there's a lot of people that will test -mm version,
> >> > especially on production servers - -mm is a little bit too unstable.
> >>
> >> Any chance to get this patch against 2.6.17-rc4-mm3?
> >
> >yes, reiser4 updates for latest stock and mm kernels will be out in one
> >or two days
> >
> There is a version out for 2.6.17-rc4-mm1, but for stock kernel? Has the latter
> been canceled?
>
There is quite fresh
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.16/reiser4-for-2.6.16-4.patch.gz
>
> Jan Engelhardt
next prev parent reply other threads:[~2006-06-08 12:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 20:14 Hans Reiser
2006-05-23 20:26 ` Alexey Polyakov
2006-05-23 20:33 ` Michal Piotrowski
2006-05-24 14:39 ` Vladimir V. Saveliev
2006-06-08 10:45 ` Jan Engelhardt
2006-06-08 12:40 ` Vladimir V. Saveliev [this message]
2006-06-08 14:11 ` Jan Engelhardt
2006-05-24 17:53 ` Tom Vier
2006-05-24 17:55 ` Hans Reiser
2006-06-08 11:00 ` Jens Axboe
2006-06-08 11:26 ` Vladimir V. Saveliev
2006-06-08 11:35 ` Jens Axboe
2006-06-08 12:08 ` Vladimir V. Saveliev
2006-06-14 19:37 ` Hans Reiser
2006-06-08 12:10 ` Christoph Hellwig
2006-06-14 22:08 ` batched write Vladimir V. Saveliev
2006-06-17 17:04 ` Andrew Morton
2006-06-17 17:51 ` Hans Reiser
2006-06-18 11:20 ` Nix
2006-06-19 9:05 ` Hans Reiser
2006-06-19 11:32 ` Miklos Szeredi
2006-06-19 16:39 ` Hans Reiser
2006-06-19 17:35 ` Miklos Szeredi
2006-06-19 17:52 ` Akshat Aranya
2006-06-19 20:39 ` Hans Reiser
2006-06-19 16:27 ` Andreas Dilger
2006-06-19 16:51 ` Hans Reiser
2006-06-19 18:50 ` Andreas Dilger
2006-06-19 20:47 ` Hans Reiser
2006-06-20 0:01 ` David Chinner
2006-06-20 7:19 ` Hans Reiser
2006-06-20 7:26 ` Andrew Morton
2006-06-20 9:02 ` Steven Whitehouse
2006-06-20 16:26 ` Vladimir V. Saveliev
2006-06-20 17:29 ` Hans Reiser
2006-06-19 18:28 ` Vladimir V. Saveliev
2006-05-24 17:59 ` [PATCH] updated reiser4 - reduced cpu usage for writes by writing more than 4k at a time (has implications for generic write code and eventually for the IO layer) Hans Reiser
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=1149770440.6336.39.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=Reiserfs-Dev@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=akpm@osdl.org \
--cc=alexey.polyakov@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=ndiller@namesys.com \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®