From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Frank Yang <frank.yangjie@gmail.com>
Cc: Isaku Yamahata <yamahata@private.email.ne.jp>,
qemu-stable@nongnu.org, qemu-devel@nongnu.org,
yamahata@valinux.co.jp, Michael R Hines <mrhines@us.ibm.com>,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [Qemu-stable][PATCH] rdma: fix multiple VMs parallel migration
Date: Tue, 03 Sep 2013 10:13:54 -0400 [thread overview]
Message-ID: <5225EEA2.4060908@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAO0YQGKOOtghkz8e4+d4sS_Y9bJoQfYpASAKx7YgWq5E6M7mrw@mail.gmail.com>
No top-posting, please.
On 09/03/2013 12:20 AM, Frank Yang wrote:
> Yes, it depends on low-level implementation. During my earlier test,
> using one CQ to send and receive may cause packet loss with heavy load:
> the destination thinks it send READY message successfully but the source
> still waits for it. This situation always happens when the destination
> polls
> receive CQE first.
>
> So I think using only one CQ may cause packet conflict or something
> like that,
> and it should be the driver bug. However, using two CQs fix the problem.
>
>
This doesn't seem like a very clear answer ..... are you sure its packet
loss?
The queue pairs are supposed to be reliable - I've never experienced a
situation
where packets were simply "dropped" for no reason without breaking the
connection and putting the QP into an error state.
- Michael
next prev parent reply other threads:[~2013-09-03 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 12:39 [Qemu-devel] [Qemu-stable][PATCH] rdma: fix multiple VMs parallel migration Frank Yang
2013-09-02 12:46 ` Isaku Yamahata
2013-09-03 4:20 ` Frank Yang
2013-09-03 5:38 ` Lei Li
2013-09-04 3:59 ` Frank Yang
2013-09-03 14:13 ` Michael R. Hines [this message]
2013-09-04 3:23 ` Frank Yang
2013-09-03 5:03 ` Lei Li
2013-09-04 2:42 ` Frank Yang
2013-09-04 8:10 ` Frank Yang
2013-09-24 17:59 ` [Qemu-devel] [Qemu-stable] [PATCH] " Michael R. Hines
2013-10-10 13:38 ` Frank Yang
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=5225EEA2.4060908@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=frank.yangjie@gmail.com \
--cc=mrhines@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=yamahata@private.email.ne.jp \
--cc=yamahata@valinux.co.jp \
/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.