From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] block-commit & dropping privs
Date: Mon, 30 Mar 2015 17:36:34 +0200 [thread overview]
Message-ID: <20150330153634.GC4305@noname.redhat.com> (raw)
In-Reply-To: <55158F8B.9090607@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Am 27.03.2015 um 18:12 hat Eric Blake geschrieben:
> On 03/27/2015 09:36 AM, Michael Tokarev wrote:
> > Wonder how to specify cache mode, or should I open these with proper
> > O_DIRECT/O_SYNC/whatever? It looks like it's possible to change O_DIRECT
> > at runtime but not O_SYNC.
> >
> > And the more interesting question is how to do that from shell.
>
> Redirections only get you so far in shell; you may need a wrapper C
> program go get O_DIRECT and/or O_SYNC pre-set. Then again, if you use
> QMP and pass over the Unix socket, you need a C program anyways.
O_DIRECT can be set with fcntl(), so qemu takes care of that. O_SYNC
is completely unused on Linux these days, so that shouldn't be a problem
either. (Other platforms use it as a misguided attempt of approximating
O_DIRECT. We should really error out instead.)
So if I'm not mistaken, just having one read-only and one read-write fd
should be enough for any configuration in practice.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-03-30 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:07 [Qemu-devel] block-commit & dropping privs Michael Tokarev
2015-03-27 14:49 ` Eric Blake
2015-03-27 15:36 ` Michael Tokarev
2015-03-27 17:12 ` Eric Blake
2015-03-30 15:36 ` Kevin Wolf [this message]
2015-04-01 9:26 ` Michael Tokarev
2015-04-01 9:54 ` Michael Tokarev
2015-04-01 12:34 ` Kevin Wolf
2015-04-02 10:58 ` Michael Tokarev
2015-04-02 11:24 ` Kevin Wolf
2015-04-02 12:04 ` Michael Tokarev
2015-04-02 13:07 ` Eric Blake
2015-04-03 4:28 ` Jeff Cody
2015-04-03 19:49 ` Eric Blake
2015-04-03 19:57 ` Jeff Cody
2015-04-02 13:19 ` Kevin Wolf
2015-04-06 15:37 ` Michael Tokarev
2015-04-07 9:24 ` Kevin Wolf
2015-04-03 3:59 ` Jeff Cody
2015-04-07 9:18 ` Kevin Wolf
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=20150330153634.GC4305@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).