qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-block@nongnu.org, Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com,
	qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qed: fix bdrv_qed_drain
Date: Mon, 7 Mar 2016 17:57:41 +0100	[thread overview]
Message-ID: <20160307165741.GB6464@noname.redhat.com> (raw)
In-Reply-To: <56CC647A.6020803@redhat.com>

Am 23.02.2016 um 14:54 hat Paolo Bonzini geschrieben:
> 
> 
> On 23/02/2016 13:49, Fam Zheng wrote:
> > On Tue, 02/23 11:43, Paolo Bonzini wrote:
> >>
> >>
> >> On 23/02/2016 06:57, Fam Zheng wrote:
> >>>>>> +        qed_cancel_need_check_timer(s);
> >>>>>> +        qed_need_check_timer_cb(s);
> >>>>>> +    }
> >>>>>
> >>>>> What if an allocating write is queued (the else branch case)? Its completion
> >>>>> will be in bdrv_drain and it could arm the need_check_timer which is wrong.
> >>>>>
> >>>>> We need to drain the allocating_write_reqs queue before checking the timer.
> >>>>
> >>>> You're right, but how?  That's what bdrv_drain(bs) does, it's a
> >>>> chicken-and-egg problem.
> >>>
> >>> Maybe use an aio_poll loop before the if?
> >>
> >> That would not change the fact that you're reimplementing bdrv_drain
> >> inside bdrv_qed_drain.
> > 
> > But it fulfills the contract of .bdrv_drain. This is the easy way, the hard way
> > would be iterating through the allocating_write_reqs list and process reqs one
> > by one synchronously, which still involves aio_poll indirectly.
> 
> The easy way would be better then.
> 
> Stefan, any second opinion?

What's the status here? It would be good to have qed not segfaulting all
the time.

Kevin

  reply	other threads:[~2016-03-07 16:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 15:53 [Qemu-devel] [PATCH] qed: fix bdrv_qed_drain Paolo Bonzini
2016-02-17  2:57 ` Fam Zheng
2016-02-17 11:28   ` Paolo Bonzini
2016-02-23  5:57     ` Fam Zheng
2016-02-23 10:43       ` Paolo Bonzini
2016-02-23 12:49         ` Fam Zheng
2016-02-23 13:54           ` Paolo Bonzini
2016-03-07 16:57             ` Kevin Wolf [this message]
2016-03-07 20:56               ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-03-07 21:22                 ` [Qemu-devel] " Paolo Bonzini
2016-03-08  9:52                   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-03-08  9:59                     ` Kevin Wolf
2016-03-08  9:58                 ` Kevin Wolf
2016-03-09 15:37                   ` Stefan Hajnoczi
2016-03-07 20:57               ` Stefan Hajnoczi

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=20160307165741.GB6464@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).