qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4367] Align file accesses with cache=off (Kevin Wolf, Laurent Vivier)
Date: Wed, 7 May 2008 19:19:13 +0300	[thread overview]
Message-ID: <f43fc5580805070919h20ecf4f4k3028dd4fc4102251@mail.gmail.com> (raw)
In-Reply-To: <4821A8F0.9070506@suse.de>

On 5/7/08, Kevin Wolf <kwolf@suse.de> wrote:
> 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.

Good point. For most patches sent to the list I don't have strong
opinions, for example I don't know the necessary technical background
or the patch could affect areas that I'm not interested in. Maybe if I
comment on the patches it gives a wrong signal about the future
prospects for the patch getting committed. I still think it is a waste
of resources if the effort made for the patches gets lost or don't get
much review like what is happening here very often.

Usually I run a set of tests before committing. From the amount of
breakage fixes and reverts I get the impression that some of the other
developers test less. Though testing will not catch all deeper
problems like in this case.

Maybe more developers with strong focus on x86/x86_64 host and target
would help.

  reply	other threads:[~2008-05-07 16:19 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 [this message]
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=f43fc5580805070919h20ecf4f4k3028dd4fc4102251@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --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).