From: Oleg Drokin <green@namesys.com>
To: Christian Stuke <chstuke@exinferis.de>
Cc: berthiaume_wayne@emc.com, reiserfs-list@namesys.com
Subject: Re: fsync() Performance Issue
Date: Thu, 2 May 2002 10:20:02 +0400 [thread overview]
Message-ID: <20020502102002.A5253@namesys.com> (raw)
In-Reply-To: <006d01c1f197$3dd0bbd0$fe78a8c0@exinferis>
Hello!
On Thu, May 02, 2002 at 07:07:18AM +0200, Christian Stuke wrote:
> Could we have this for 2.4.18+ pending also please?
This patch would apply to 2.4.18 + pending patches, I believe.
As for including these patchs into pending queue for 2.4.18, this is impossible
now, it is too big of a change, unfortunatelly. We hope to get something
like this into 2.4.19-pre1+
Bye,
Oleg
next prev parent reply other threads:[~2002-05-02 6:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 20:28 fsync() Performance Issue berthiaume_wayne
2002-04-29 16:20 ` Russell Coker
2002-04-29 16:30 ` Chris Mason
2002-04-29 16:32 ` Toby Dickenson
2002-04-29 16:45 ` Chris Mason
2002-04-29 17:56 ` Matthias Andree
2002-04-29 18:58 ` Valdis.Kletnieks
2002-04-29 18:56 ` Hans Reiser
2002-04-30 14:20 ` Oleg Drokin
2002-04-30 14:27 ` Chris Mason
2002-05-02 5:07 ` Christian Stuke
2002-05-02 6:20 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 17:26 berthiaume_wayne
2002-04-30 14:45 berthiaume_wayne
2002-05-03 20:35 berthiaume_wayne
2002-05-03 22:00 ` Chris Mason
2002-05-04 2:05 ` Hans Reiser
2002-05-04 5:41 ` Valdis.Kletnieks
2002-05-04 13:11 ` Chris Mason
2002-05-04 14:59 ` Hans Reiser
2002-05-06 12:40 ` Chris Mason
2002-05-06 13:02 ` Hans Reiser
2002-05-06 21:21 ` Hans Reiser
2002-05-06 22:57 ` Chris Mason
2002-05-06 23:41 ` Hans Reiser
2002-05-07 1:17 ` Manuel Krause
2002-05-07 2:04 ` Chris Mason
2002-05-07 20:26 ` Manuel Krause
2002-05-08 1:22 ` Chris Mason
2002-05-06 12:54 berthiaume_wayne
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=20020502102002.A5253@namesys.com \
--to=green@namesys.com \
--cc=berthiaume_wayne@emc.com \
--cc=chstuke@exinferis.de \
--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.