From: Andrew Morton <akpm@zip.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: synchronous mounts
Date: Fri, 16 Nov 2001 00:33:32 -0800 [thread overview]
Message-ID: <3BF4CF5C.18CBE4BC@zip.com.au> (raw)
In-Reply-To: <3BF376EC.EA9B03C8@zip.com.au> <20011115214525.C14221@redhat.com> <3BF45B9F.DEE1076B@mandrakesoft.com>
Jeff Garzik wrote:
>
> As it stands, it seems like redefining 'sync' to sync less data than is
> currently done is not only changing current behavior, but providing less
> to users overall.
>
Persuasively argued. You appear to have your wish, as this
patch was merged in -pre5.
A `dirsync' option does make sense though, for the reasons which
Stephen outlined.
The whole handling of synchronous operations needs a rip-up-and-rewrite
anyway. We're currently holding onto a stack of locks while waiting
for the disk to spin round and round. It's a great scalability bottleneck
for multiple threads doing things in the same directory. This is
something I shall look at when the kernel versions turn odd.
-
next prev parent reply other threads:[~2001-11-16 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 8:03 synchronous mounts Andrew Morton
2001-11-15 21:45 ` Stephen C. Tweedie
2001-11-15 22:02 ` Andrew Morton
2001-11-15 23:05 ` Stephen C. Tweedie
2001-11-16 0:19 ` Jeff Garzik
2001-11-16 8:33 ` Andrew Morton [this message]
2001-11-16 10:47 ` Matthias Andree
2001-11-16 12:28 ` Stephen C. Tweedie
2001-11-16 13:28 ` Jeff Garzik
2001-11-16 13:37 ` Jeff Garzik
2001-11-16 22:40 ` Matthias Andree
2001-11-16 3:07 ` Neil Brown
2001-11-17 7:13 ` Andrew Morton
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=3BF4CF5C.18CBE4BC@zip.com.au \
--to=akpm@zip.com.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--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