From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Isaku Yamahata <yamahata@private.email.ne.jp>
Cc: owasserm@redhat.com, quintela@redhat.com, mrhines@us.ibm.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] rdma: qemu_rdma_post_send_control uses wrongly RDMA_WRID_MAX
Date: Fri, 02 Aug 2013 09:40:20 -0400 [thread overview]
Message-ID: <51FBB6C4.3070905@linux.vnet.ibm.com> (raw)
In-Reply-To: <ea73c53d3a14ae38c1c8821fa39bb1c8b0c83d28.1375415452.git.yamahata@private.email.ne.jp>
On 08/01/2013 11:56 PM, Isaku Yamahata wrote:
> RDMA_WRID_CONTROL should be used. And remove related work around.
>
> Cc: Michael R. Hines <mrhines@us.ibm.com>
> Signed-off-by: Isaku Yamahata <yamahata@private.email.ne.jp>
> ---
> migration-rdma.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/migration-rdma.c b/migration-rdma.c
> index edbae9f..67069d2 100644
> --- a/migration-rdma.c
> +++ b/migration-rdma.c
> @@ -322,7 +322,7 @@ typedef struct RDMAContext {
> char *host;
> int port;
>
> - RDMAWorkRequestData wr_data[RDMA_WRID_MAX + 1];
> + RDMAWorkRequestData wr_data[RDMA_WRID_MAX];
>
> /*
> * This is used by *_exchange_send() to figure out whether or not
> @@ -1397,7 +1397,7 @@ static int qemu_rdma_post_send_control(RDMAContext *rdma, uint8_t *buf,
> RDMAControlHeader *head)
> {
> int ret = 0;
> - RDMAWorkRequestData *wr = &rdma->wr_data[RDMA_WRID_MAX];
> + RDMAWorkRequestData *wr = &rdma->wr_data[RDMA_WRID_CONTROL];
> struct ibv_send_wr *bad_wr;
> struct ibv_sge sge = {
> .addr = (uint64_t)(wr->control),
> @@ -2052,7 +2052,7 @@ static void qemu_rdma_cleanup(RDMAContext *rdma)
> g_free(rdma->block);
> rdma->block = NULL;
>
> - for (idx = 0; idx <= RDMA_WRID_MAX; idx++) {
> + for (idx = 0; idx < RDMA_WRID_MAX; idx++) {
> if (rdma->wr_data[idx].control_mr) {
> rdma->total_registrations--;
> ibv_dereg_mr(rdma->wr_data[idx].control_mr);
> @@ -2134,7 +2134,7 @@ static int qemu_rdma_source_init(RDMAContext *rdma, Error **errp, bool pin_all)
> goto err_rdma_source_init;
> }
>
> - for (idx = 0; idx <= RDMA_WRID_MAX; idx++) {
> + for (idx = 0; idx < RDMA_WRID_MAX; idx++) {
> ret = qemu_rdma_reg_control(rdma, idx);
> if (ret) {
> ERROR(temp, "rdma migration: error registering %d control!\n",
> @@ -2243,7 +2243,7 @@ static int qemu_rdma_dest_init(RDMAContext *rdma, Error **errp)
> struct rdma_cm_id *listen_id;
> char ip[40] = "unknown";
>
> - for (idx = 0; idx <= RDMA_WRID_MAX; idx++) {
> + for (idx = 0; idx < RDMA_WRID_MAX; idx++) {
> rdma->wr_data[idx].control_len = 0;
> rdma->wr_data[idx].control_curr = NULL;
> }
> @@ -2696,7 +2696,7 @@ static int qemu_rdma_accept(RDMAContext *rdma)
> goto err_rdma_dest_wait;
> }
>
> - for (idx = 0; idx <= RDMA_WRID_MAX; idx++) {
> + for (idx = 0; idx < RDMA_WRID_MAX; idx++) {
> ret = qemu_rdma_reg_control(rdma, idx);
> if (ret) {
> fprintf(stderr, "rdma: error registering %d control!\n", idx);
Good eyes ...... I totally missed that =)
Reviewed-by: Michael R. Hines <mrhines@us.ibm.com>
next prev parent reply other threads:[~2013-08-02 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 3:56 [Qemu-devel] [PATCH 0/3] rdma fixes and clean ups Isaku Yamahata
2013-08-02 3:56 ` [Qemu-devel] [PATCH 1/3] rdma: don't use negative index to array Isaku Yamahata
2013-08-02 13:28 ` Michael R. Hines
2013-08-02 3:56 ` [Qemu-devel] [PATCH 2/3] rdma: qemu_rdma_post_send_control uses wrongly RDMA_WRID_MAX Isaku Yamahata
2013-08-02 13:40 ` Michael R. Hines [this message]
2013-08-02 3:56 ` [Qemu-devel] [PATCH 3/3] rdma: use RDMA_WRID_READY Isaku Yamahata
2013-08-02 13:40 ` Michael R. Hines
2013-08-02 13:40 ` [Qemu-devel] [PATCH 0/3] rdma fixes and clean ups Michael R. Hines
2013-08-04 1:24 ` Isaku Yamahata
2013-08-04 2:55 ` Michael R. Hines
2013-08-14 16:28 ` Anthony Liguori
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=51FBB6C4.3070905@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yamahata@private.email.ne.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 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).