From: Christoph Hellwig <hch@infradead.org>
To: Sage Weil <sage@newdream.net>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph updates for 3.1-rc1
Date: Sun, 31 Jul 2011 14:35:56 -0400 [thread overview]
Message-ID: <20110731183556.GA23133@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1107261152440.2593@cobra.newdream.net>
On Tue, Jul 26, 2011 at 01:36:37PM -0700, Sage Weil wrote:
> Sage Weil (19):
> ceph: add flags field to file_info
> ceph: add F_SYNC file flag to force sync (non-O_DIRECT) io
Can you document what the exact semantics of this flag are, and how
they different from using O_SYNC/O_DSYNC.
next prev parent reply other threads:[~2011-07-31 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 20:36 [GIT PULL] Ceph updates for 3.1-rc1 Sage Weil
2011-07-31 18:35 ` Christoph Hellwig [this message]
2011-08-01 4:53 ` Sage Weil
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=20110731183556.GA23133@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.net \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).