From: Chuck Lever <cel@monkey.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCHES]
Date: Thu, 27 May 1999 15:55:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSF.4.03.9905271552420.16505-100000@funky.monkey.org> (raw)
In-Reply-To: <14156.58667.141026.238904@dukat.scot.redhat.com>
On Thu, 27 May 1999, Stephen C. Tweedie wrote:
> However, this brings up another point:
>
> ftp://ftp.uk.linux.org/pub/linux/sct/fs/misc/fsync-2.2.8-v5.diff
>
> is a set of diffs to fix fsync performance on 2.2. It fully implements
> fsync and fdatasync, and applies the same optimisations to O_SYNC. It
> uses per-inode dirty buffer lists.
stephen -
this patch appears to combine the "block allocation deadlock" patch with
the original fsync reimplementation... correct?
have you experienced and/or fixed the 5-second self-destruct problem i
mentioned to you?
- Chuck Lever
--
corporate: <chuckl@netscape.com>
personal: <chucklever@netscape.net> or <cel@monkey.org>
The Linux Scalability project:
http://www.citi.umich.edu/projects/linux-scalability/
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-05-27 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 3:36 [PATCHES] Eric W. Biederman
1999-05-23 6:03 ` [PATCHES] Linus Torvalds
1999-05-23 14:54 ` [PATCHES] Eric W. Biederman
1999-05-23 15:49 ` [PATCHES] Ingo Molnar
1999-05-23 18:34 ` [PATCHES] Eric W. Biederman
1999-05-27 6:24 ` [PATCHES] Stephen C. Tweedie
1999-05-27 19:55 ` Chuck Lever [this message]
1999-05-27 23:39 ` [PATCHES] Stephen C. Tweedie
1999-05-28 5:30 ` [PATCHES] Chuck Lever
1999-05-29 1:24 ` [PATCHES] Stephen C. Tweedie
1999-05-30 17:01 ` [PATCHES] Eric W. Biederman
1999-05-27 6:25 ` [PATCHES] Stephen C. Tweedie
1999-05-24 17:20 ` [PATCHES] Manfred Spraul
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=Pine.BSF.4.03.9905271552420.16505-100000@funky.monkey.org \
--to=cel@monkey.org \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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