From: Yuval Shaia <yuval.shaia@oracle.com>
To: Kamal Heib <kamalheib1@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/4] pvrdma: Add support for SRQ
Date: Sun, 7 Apr 2019 12:15:04 +0300 [thread overview]
Message-ID: <20190407091503.GB6737@lap1> (raw)
In-Reply-To: <20190403181937.GE3446@lap1>
On Wed, Apr 03, 2019 at 09:19:38PM +0300, Yuval Shaia wrote:
> On Wed, Apr 03, 2019 at 02:33:39PM +0300, Kamal Heib wrote:
> > This series implements the SRQ (Shared Receive Queue) for the pvrdma
> > device, It also includes all the needed functions and definitions for
> > support SRQ in the backend and resource management layers.
> >
> > Changes from v2->3:
> > - Patch #1:
> > -- Fix commit message.
> > -- Remove initialization of backend_qp from rdma_backend_post_srq_recv().
> > -- Add rx_srq counter.
> > - Patch #2:
> > -- Add checks for srq attrs.
> > - Patch #3:
> > -- Move initialization of recv_cq_handle to be under is_srq.
> > -- Rearrange destroy_qp() to avoid use after free.
> > - Patch #4:
> > -- Avoid use after free.
> > -- Fix indentation.
> >
> > Changes from v1->v2:
> > - Handle checkpatch.pl warnings.
>
> Appreciate if you can post v4 with a new patch to display the new counter
> (function rdma_dump_device_counters).
Please ignore this comment, counter is already added - i missed that.
With that - patchset lgtm, from my perspective ready to merge.
>
> >
> > Kamal Heib (4):
> > hw/rdma: Add SRQ support to backend layer
> > hw/rdma: Add support for managing SRQ resource
> > hw/rdma: Modify create/destroy QP to support SRQ
> > hw/pvrdma: Add support for SRQ
> >
> > hw/rdma/rdma_backend.c | 125 +++++++++++++++++++++-
> > hw/rdma/rdma_backend.h | 18 +++-
> > hw/rdma/rdma_backend_defs.h | 5 +
> > hw/rdma/rdma_rm.c | 117 +++++++++++++++++++-
> > hw/rdma/rdma_rm.h | 13 ++-
> > hw/rdma/rdma_rm_defs.h | 10 ++
> > hw/rdma/vmw/pvrdma_cmd.c | 206 ++++++++++++++++++++++++++++++++----
> > hw/rdma/vmw/pvrdma_main.c | 16 +++
> > hw/rdma/vmw/pvrdma_qp_ops.c | 46 +++++++-
> > hw/rdma/vmw/pvrdma_qp_ops.h | 1 +
> > 10 files changed, 521 insertions(+), 36 deletions(-)
> >
> > --
> > 2.20.1
> >
> >
>
next prev parent reply other threads:[~2019-04-07 9:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 11:33 [Qemu-devel] [PATCH v3 0/4] pvrdma: Add support for SRQ Kamal Heib
2019-04-03 11:33 ` [Qemu-devel] [PATCH v3 1/4] hw/rdma: Add SRQ support to backend layer Kamal Heib
2019-04-03 18:05 ` Yuval Shaia
2019-04-07 8:13 ` Kamal Heib
2019-04-07 8:13 ` Kamal Heib
2019-04-07 9:13 ` Yuval Shaia
2019-04-07 9:13 ` Yuval Shaia
2019-04-03 11:33 ` [Qemu-devel] [PATCH 2/4] hw/rdma: Add support for managing SRQ resource Kamal Heib
2019-04-03 18:10 ` Yuval Shaia
2019-04-03 11:33 ` [Qemu-devel] [PATCH v3 3/4] hw/rdma: Modify create/destroy QP to support SRQ Kamal Heib
2019-04-03 18:15 ` Yuval Shaia
2019-04-03 11:33 ` [Qemu-devel] [PATCH v3 4/4] hw/pvrdma: Add support for SRQ Kamal Heib
2019-04-03 18:16 ` Yuval Shaia
2019-04-03 18:19 ` [Qemu-devel] [PATCH v3 0/4] pvrdma: " Yuval Shaia
2019-04-07 9:15 ` Yuval Shaia [this message]
2019-04-07 9:15 ` Yuval Shaia
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=20190407091503.GB6737@lap1 \
--to=yuval.shaia@oracle.com \
--cc=kamalheib1@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).