From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Ben LaHaise <bcrl@redhat.com>
Subject: Re: [patch] O_SYNC patch 3/3, add inode dirty buffer list support to ext2
Date: Thu, 23 Nov 2000 12:01:35 +0000 [thread overview]
Message-ID: <20001123120135.D8368@redhat.com> (raw)
In-Reply-To: <20001122112646.D6516@redhat.com> <20001122115424.A18592@vger.timpanogas.org>
In-Reply-To: <20001122115424.A18592@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Wed, Nov 22, 2000 at 11:54:24AM -0700
Hi,
On Wed, Nov 22, 2000 at 11:54:24AM -0700, Jeff V. Merkey wrote:
>
> I have not implemented O_SYNC in NWFS, but it looks like I need to add it
> before posting the final patches. This patch appears to force write-through
> of only dirty inodes, and allow reads to continue from cache. Is this
> assumption correct
Yes: O_SYNC is not required to force reads to be made from disk.
SingleUnix has an "O_RSYNC" option which does that, but O_SYNC and
O_DSYNC don't imply that.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 11:26 [patch] O_SYNC patch 3/3, add inode dirty buffer list support to ext2 Stephen C. Tweedie
2000-11-22 18:54 ` Jeff V. Merkey
2000-11-22 22:20 ` Josue Emmanuel Amaro
2000-11-23 12:01 ` Stephen C. Tweedie [this message]
2000-11-23 20:01 ` Jeff V. Merkey
2000-11-24 18:07 ` Andrea Arcangeli
2000-11-24 23:32 ` Eric W. Biederman
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=20001123120135.D8368@redhat.com \
--to=sct@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.