From: Leon Romanovsky <leon@kernel.org>
To: Long Li <longli@microsoft.com>
Cc: "longli@linuxonhyperv.com" <longli@linuxonhyperv.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Ajay Sharma <sharmaajay@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Patch v4 0/3] Register with RDMA SOC interface and support for CQ
Date: Wed, 20 Dec 2023 09:40:18 +0200 [thread overview]
Message-ID: <20231220074018.GA136797@unreal> (raw)
In-Reply-To: <PH7PR21MB3263ADBB8113D2BF2DDC0552CE90A@PH7PR21MB3263.namprd21.prod.outlook.com>
On Mon, Dec 18, 2023 at 06:23:21PM +0000, Long Li wrote:
> > Subject: Re: [Patch v4 0/3] Register with RDMA SOC interface and support for CQ
> >
> > On Fri, Dec 15, 2023 at 06:04:12PM -0800, longli@linuxonhyperv.com wrote:
> > > From: Long Li <longli@microsoft.com>
> > >
> > > This patchset add support for registering a RDMA device with SoC for
> > > support of querying device capabilities, upcoming RC queue pairs and
> > > CQ interrupts.
> > >
> > > This patchset is partially based on Ajay Sharma's work:
> > > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore
> > > .kernel.org%2Fnetdev%2F1697494322-26814-1-git-send-email-sharmaajay%40
> > >
> > linuxonhyperv.com&data=05%7C02%7Clongli%40microsoft.com%7Caaadcacece2
> > b
> > >
> > 44117bfd08dbff03b2c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C
> > 6383
> > >
> > 84163586869634%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> > QIjoiV2l
> > >
> > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4G1tI9
> > VOTGv
> > > rA3UF6YQZ%2BM2uDDd71sZpejOvhl2y60%3D&reserved=0
> > >
> > > Changes in v2:
> > > Dropped the patches to create EQs for RC QP. They will be implemented
> > > with RC patches.
> >
> > You sent twice v2, never sent v3 and two days later sent v4 without even
> > explaining why.
> >
> > Can you please invest time and write more detailed changelog which will include
> > v2, v3 and v4 changes?
> >
> > Tanks
>
> I'm sorry, the cover letter for the 2nd v2 should be v3 (it was a typo). The rest of the patches in that series are correctly labeled as v3.
>
> For v3 and v4, I put the change log in the individual patches, as there are no changes to the cover letter. If you think I should put change logs in the cover letter, please let me know.
For the future submission, yes, please write changelog in the cover letter.
Thanks
>
> Subject: [Patch v4 2/3] RDMA/mana_ib: query device capabilities
> Change in v4:
> On query device failure, goto deregister_device, not ib_free_device
> Change function name mana_ib_query_adapter_caps() to mana_ib_gd_query_adapter_caps() to better reflect this is a HWC request
>
> Subject: [Patch v4 3/3] RDMA/mana_ib: Add CQ interrupt support for RAW QP
> Change in v3:
> Removed unused varaible mana_ucontext in mana_ib_create_qp_rss().
> Simplified error handling in mana_ib_create_qp_rss() on failure to allocate queues for rss table.
>
> Thanks,
>
> Long
>
> >
> > >
> > >
> > > Long Li (3):
> > > RDMA/mana_ib: register RDMA device with GDMA
> > > RDMA/mana_ib: query device capabilities
> > > RDMA/mana_ib: Add CQ interrupt support for RAW QP
> > >
> > > drivers/infiniband/hw/mana/cq.c | 34 ++++++-
> > > drivers/infiniband/hw/mana/device.c | 31 +++++--
> > > drivers/infiniband/hw/mana/main.c | 69 ++++++++++----
> > > drivers/infiniband/hw/mana/mana_ib.h | 53 +++++++++++
> > > drivers/infiniband/hw/mana/qp.c | 90 ++++++++++++++++---
> > > .../net/ethernet/microsoft/mana/gdma_main.c | 5 ++
> > > include/net/mana/gdma.h | 5 ++
> > > 7 files changed, 252 insertions(+), 35 deletions(-)
> > >
> > > --
> > > 2.25.1
> > >
next prev parent reply other threads:[~2023-12-20 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 2:04 [Patch v4 0/3] Register with RDMA SOC interface and support for CQ longli
2023-12-16 2:04 ` [Patch v4 1/3] RDMA/mana_ib: register RDMA device with GDMA longli
2023-12-16 2:04 ` [Patch v4 2/3] RDMA/mana_ib: query device capabilities longli
2023-12-16 2:04 ` [Patch v4 3/3] RDMA/mana_ib: Add CQ interrupt support for RAW QP longli
2023-12-17 13:25 ` [Patch v4 0/3] Register with RDMA SOC interface and support for CQ Leon Romanovsky
2023-12-18 18:23 ` Long Li
2023-12-20 7:40 ` Leon Romanovsky [this message]
2023-12-20 8:27 ` Leon Romanovsky
2023-12-20 8:30 ` Leon Romanovsky
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=20231220074018.GA136797@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharmaajay@microsoft.com \
--cc=wei.liu@kernel.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).