From: MORITA Kazutaka <morita.kazutaka@gmail.com>
To: Liu Yuan <namei.unix@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [sheepdog] [PATCH v3 07/10] sheepdog: try to reconnect to sheepdog after network error
Date: Thu, 25 Jul 2013 21:53:14 +0900 [thread overview]
Message-ID: <m2mwparebp.wl%morita.kazutaka@gmail.com> (raw)
In-Reply-To: <20130725091346.GD2604@ubuntu-precise>
At Thu, 25 Jul 2013 17:13:46 +0800,
Liu Yuan wrote:
>
> > +
> > + /* Try to reconnect the sheepdog server every one second. */
> > + while (s->fd < 0) {
> > + s->fd = get_sheep_fd(s);
> > + if (s->fd < 0) {
> > + dprintf("Wait for connection to be established\n");
> > + co_aio_sleep_ns(1000000000ULL);
> > + }
> > + };
> > +
> > + /* Move all the inflight requests to the failed queue. */
> > + QLIST_FOREACH_SAFE(aio_req, &s->inflight_aio_head, aio_siblings, next) {
> > + QLIST_REMOVE(aio_req, aio_siblings);
> > + QLIST_INSERT_HEAD(&s->failed_aio_head, aio_req, aio_siblings);
> > + }
> > +
> > + /* Resend all the failed aio requests. */
> > + while (!QLIST_EMPTY(&s->failed_aio_head)) {
> > + aio_req = QLIST_FIRST(&s->failed_aio_head);
> > + QLIST_REMOVE(aio_req, aio_siblings);
> > + QLIST_INSERT_HEAD(&s->inflight_aio_head, aio_req, aio_siblings);
> > + resend_aioreq(s, aio_req);
> > + }
> > +}
> > +
>
> Is failed queue necessary? Here you just move requests from inflight queue to
> failed queue, then interate the failed queue to send them all.
>
> Isn't it simpler we just resend the requests in the inflight queue like
>
> > + QLIST_FOREACH(aio_req, &s->inflight_aio_head, aio_siblings, next) {
> > + resend_aioreq(s, aio_req);
> > + }
resend_aioreq() can yield and a new aio request can be added to the
inflight queue during this loop. To avoid mixing new requests and
failed ones, I think the failed queue is necessary.
Thanks,
Kazutaka
next prev parent reply other threads:[~2013-07-25 12:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 8:31 [Qemu-devel] [PATCH v3 00/10] sheepdog: reconnect server after connection failure MORITA Kazutaka
2013-07-25 8:31 ` [Qemu-devel] [PATCH v3 01/10] ignore SIGPIPE in qemu-img and qemu-io MORITA Kazutaka
2013-07-25 8:31 ` [Qemu-devel] [PATCH v3 02/10] iov: handle EOF in iov_send_recv MORITA Kazutaka
2013-07-25 8:31 ` [Qemu-devel] [PATCH v3 03/10] sheepdog: check return values of qemu_co_recv/send correctly MORITA Kazutaka
2013-07-25 8:46 ` Liu Yuan
2013-07-25 8:53 ` [Qemu-devel] [sheepdog] " MORITA Kazutaka
2013-07-25 8:56 ` [Qemu-devel] " Liu Yuan
2013-07-25 8:31 ` [Qemu-devel] [PATCH v3 04/10] sheepdog: handle vdi objects in resend_aio_req MORITA Kazutaka
2013-07-25 8:32 ` [Qemu-devel] [PATCH v3 05/10] sheepdog: reload inode outside of resend_aioreq MORITA Kazutaka
2013-07-25 8:32 ` [Qemu-devel] [PATCH v3 06/10] coroutine: add co_aio_sleep_ns() to allow sleep in block drivers MORITA Kazutaka
2013-07-25 8:32 ` [Qemu-devel] [PATCH v3 07/10] sheepdog: try to reconnect to sheepdog after network error MORITA Kazutaka
2013-07-25 9:13 ` Liu Yuan
2013-07-25 12:53 ` MORITA Kazutaka [this message]
2013-07-25 13:20 ` [Qemu-devel] [sheepdog] " Liu Yuan
2013-07-26 5:53 ` MORITA Kazutaka
2013-07-25 8:32 ` [Qemu-devel] [PATCH v3 08/10] sheepdog: make add_aio_request and send_aioreq void functions MORITA Kazutaka
2013-07-25 8:32 ` [Qemu-devel] [PATCH v3 09/10] sheepdog: cancel aio requests if possible MORITA Kazutaka
2013-07-25 9:04 ` Liu Yuan
2013-07-25 12:54 ` [Qemu-devel] [sheepdog] " MORITA Kazutaka
2013-07-25 8:32 ` [Qemu-devel] [PATCH v3 10/10] sheepdog: check simultaneous create in resend_aioreq MORITA Kazutaka
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=m2mwparebp.wl%morita.kazutaka@gmail.com \
--to=morita.kazutaka@gmail.com \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=namei.unix@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.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).