From: Kevin Wolf <kwolf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4367] Align file accesses with cache=off (Kevin Wolf, Laurent Vivier)
Date: Wed, 07 May 2008 15:04:48 +0200 [thread overview]
Message-ID: <4821A8F0.9070506@suse.de> (raw)
In-Reply-To: <20080507123733.GA2822@shareable.org>
Jamie Lokier schrieb:
> Kevin Wolf wrote:
>> Btw, it is quite interesting to see that a serious discussion of a patch
>> happens only if it is already committed. This could have been discussed
>> a week ago when we agreed to go in the apparently wrong direction. And
>> the patch has been on the list much longer than this one week.
>
> IIRC, the same issues (recursive callback vs. queued callback,
> problems with direct and non-direct I/O in flight at the same time)
> were raised before it was committed, but it was committed anyway.
No, nobody mentioned the recursion problem. And you were talking about
problem with two different file descriptors for one file, not about the
fcntl solution. Ok, might also be that the hints were just not explicit
enough for me. ;-)
But even if so, this is more of a general feeling about how patches are
handled and not only related to this patch.
Kevin
next prev parent reply other threads:[~2008-05-07 13:09 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 [this message]
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
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=4821A8F0.9070506@suse.de \
--to=kwolf@suse.de \
--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).