From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org,
Rao Lei <lei.rao@intel.com>,
qemu-devel@nongnu.org, chen.zhang@intel.com, hreitz@redhat.com
Subject: Re: [PATCH v2] block/nbd.c: Fixed IO request coroutine not being wakeup when kill NBD server
Date: Mon, 14 Mar 2022 10:45:55 -0500 [thread overview]
Message-ID: <20220314154555.vu4ix45c4c4bvffy@redhat.com> (raw)
In-Reply-To: <b903228e-c412-a92a-2b3b-e171cfc5755f@virtuozzo.com>
On Wed, Mar 09, 2022 at 04:21:01PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 09.03.2022 10:48, Rao Lei wrote:
> > During the IO stress test, the IO request coroutine has a probability that is
> > can't be awakened when the NBD server is killed.
> >
> > The GDB stack is as follows:
> > When we do failover in COLO mode, QEMU will hang while it is waiting for
> > the in-flight IO. From the call trace, we can see the IO request coroutine
> > has yielded in nbd_co_send_request(). When we kill the NBD server, it will never
> > be wake up. Actually, when we do IO stress test, it will have a lot of
> > requests in free_sema queue. When the NBD server is killed, current
> > MAX_NBD_REQUESTS finishes with errors but they wake up at most
> > MAX_NBD_REQEUSTS from the queue. So, let's move qemu_co_queue_next out
> > to fix this issue.
> >
> > Signed-off-by: Lei Rao<lei.rao@intel.com>
>
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Thanks; will queue through my NBD tree.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2022-03-14 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 7:48 [PATCH v2] block/nbd.c: Fixed IO request coroutine not being wakeup when kill NBD server Rao Lei
2022-03-09 13:21 ` Vladimir Sementsov-Ogievskiy
2022-03-14 15:45 ` Eric Blake [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=20220314154555.vu4ix45c4c4bvffy@redhat.com \
--to=eblake@redhat.com \
--cc=chen.zhang@intel.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=lei.rao@intel.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).