qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: jamie@shareable.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4367] Align file accesses with cache=off (Kevin Wolf, Laurent Vivier)
Date: Wed, 07 May 2008 19:23:34 +0200	[thread overview]
Message-ID: <4821E596.1050306@suse.de> (raw)
In-Reply-To: <20080507162642.GA7324@shareable.org>

Jamie Lokier schrieb:
> Kevin Wolf wrote:
>> No, nobody mentioned the recursion problem.
> 
> Hmm.  I concede you're right in the sense that it was mentioned, but
> on a different thread about QEMU AIO recently :-)

Hm, okay. Will read that thread if I can find it. But I hope the 
recursion thing is fixed now anyway.

> Following the paragraph about two file descriptors, there was:
> 
>>> I'm not sure if that works, though.  On some OSes, if a file has any
>>> non-O_DIRECT open descriptor, all I/O is buffered ignoring the
>>> O_DIRECT flag.  If both are allowed simultaneously, I'm not sure what
>>> happens with cache-coherency between direct I/Os and buffered I/Os.
> 
> Not sure if that is quite the same thing :-)

Am I completely mistaken or is this still about two (or more) different 
file descriptors where one of them is non-O_DIRECT?

> I did miss that switching O_DIRECT on/off while AIOs are in flight on
> that descriptor might be dodgy (implementation dependent), and that it
> might not do the right things w.r.t. cohrency.

Me too. I just was too confident that it actually works when Laurent 
says it was better. You know, for every problem there is an answer that 
is clear, simple and wrong. ;-)

>> But even if so, this is more of a general feeling about how patches are 
>> handled and not only related to this patch.
> 
> I agree and have a similar feeling, though it's not a bad thing
> provided the issues are actually noticed, which they do seem to be.  

Actually, I do think it's a bad thing. Obviously, issues are noticed 
when the patch goes in and can be fixed then. Right. But what about the 
other 90% of the patches which don't get no attention at all? Nobody 
comments on them, they aren't committed, and after all they are wasted 
efforts.

It's a bad thing because it slows down qemu development by (passively) 
rejecting patches which are fine or could be fixed easily.

Kevin

      reply	other threads:[~2008-05-07 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 17:27 [Qemu-devel] [4367] Align file accesses with cache=off (Kevin Wolf, Laurent Vivier) Blue Swirl
2008-05-06 22:17 ` Fabrice Bellard
2008-05-06 22:33   ` Anthony Liguori
2008-05-07  7:48   ` Jamie Lokier
2008-05-07  8:16   ` Kevin Wolf
2008-05-07 12:37     ` Jamie Lokier
2008-05-07 13:04       ` Kevin Wolf
2008-05-07 16:19         ` Blue Swirl
2008-05-07 16:39           ` Kevin Wolf
2008-05-07 16:26         ` Jamie Lokier
2008-05-07 17:23           ` Kevin Wolf [this message]

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=4821E596.1050306@suse.de \
    --to=kwolf@suse.de \
    --cc=jamie@shareable.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).