From: "Fangyi (C)" <eric.fangyi@huawei.com>
To: kwolf@redhat.com, mreitz@redhat.com, pbonzini@redhat.com
Cc: wu.wubin@huawei.com, eblake@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, subo7@huawei.com, lina.lulina@huawei.com,
"jiangxiaoqing (C)" <sochin.jiang@huawei.com>
Subject: [Qemu-devel] NBD handshake may block qemu main thread when socket delays or has packet loss
Date: Wed, 4 Jan 2017 16:45:32 +0800 [thread overview]
Message-ID: <586CB62C.6080504@huawei.com> (raw)
As we all know, socket is in blocking mode when nbd is negotiating
with the other end. If the network is poor because of delay or packet
loss, socket read or write will return very slowly. The mainloop events
won't be handled in time util nbd handshake ends.
Any advices to solve the problem?
Thanks,
Regards,
FANG Yi.
next reply other threads:[~2017-01-04 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 8:45 Fangyi (C) [this message]
2017-01-04 20:44 ` [Qemu-devel] NBD handshake may block qemu main thread when socket delays or has packet loss Eric Blake
2017-01-12 14:40 ` [Qemu-devel] [Qemu-block] " 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=586CB62C.6080504@huawei.com \
--to=eric.fangyi@huawei.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=lina.lulina@huawei.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sochin.jiang@huawei.com \
--cc=subo7@huawei.com \
--cc=wu.wubin@huawei.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).