From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
qemu-stable@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qed: fix bdrv_qed_drain
Date: Tue, 8 Mar 2016 10:59:51 +0100 [thread overview]
Message-ID: <20160308095951.GC5807@noname.str.redhat.com> (raw)
In-Reply-To: <20160308095238.GA9407@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
Am 08.03.2016 um 10:52 hat Stefan Hajnoczi geschrieben:
> On Mon, Mar 07, 2016 at 10:22:58PM +0100, Paolo Bonzini wrote:
> > On 07/03/2016 21:56, Stefan Hajnoczi wrote:
> > > I think the timer concept itself is troublesome. A radical approach but
> > > limited to changing QED itself is to drop the timer and instead keep a
> > > timestamp for the last allocating write request. Next time a write
> > > request (allocating or rewriting) is about to complete, do the flush and
> > > clear the need check flag as part of the write request (if 5 seconds
> > > have passed since the timestamp).
> >
> > bdrv_qed_drain should be easy to fix in my new drain implementation,
> > which is based on draining the parent before the BdrvChild-ren. It's
> > just troublesome in the current one which alternates flushing and draining.
> >
> > I would just revert the patch that introduced bdrv_qed_drain for now,
> > and reintroduce it later (note however that something was messed up in
> > commit df9a681, "qed: Implement .bdrv_drain", 2015-11-12, because it
> > includes some dirty bitmap stuff).
>
> You're right, that might be the best solution for the time being. AFAIK
> the need check write is harmless. It does not result in a guest-visible
> change and is basically just a flush + header update.
I think it caused occasional assertion failures.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-03-08 10:00 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 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-03-07 20:56 ` 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 [this message]
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=20160308095951.GC5807@noname.str.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@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.