From: Jason Gunthorpe <jgg@nvidia.com>
To: Jack Wang <jinpu.wang@ionos.com>
Cc: linux-rdma@vger.kernel.org, bvanassche@acm.org, leon@kernel.org,
dledford@redhat.com, haris.iqbal@ionos.com
Subject: Re: [PATCHv3 for-next 0/5] Misc update for RTRS
Date: Fri, 18 Jun 2021 13:51:38 -0300 [thread overview]
Message-ID: <20210618165138.GA2052316@nvidia.com> (raw)
In-Reply-To: <20210614090337.29557-1-jinpu.wang@ionos.com>
On Mon, Jun 14, 2021 at 11:03:32AM +0200, Jack Wang wrote:
> Hi Jason, hi Doug,
>
> Please consider to include following changes to the next merge window.
> It contains:
> - first 2 patches are for reducing the memory usage when create QP.
> - the third one are to make testing on RXE working.
> - the fourth one is just cleanup for variables.
> - the last one is new to check max_qp_wr as suggested by Leon
>
> v3->v2:
> - added R-b from Leon for all 5 patches.
> - s/NOMEM/ENOMEM in patch3 commit message as suggested by Leon.
> - Rephrase the commit message for the renaming (patch4) as suggested by Leon
> v2->v1:
> - A new patch to check device map_qp_wr when create QP.
>
> v2: https://lore.kernel.org/linux-rdma/20210611121034.48837-1-jinpu.wang@ionos.com/T/#t
> v1: https://lore.kernel.org/linux-rdma/20210608103039.39080-1-jinpu.wang@ionos.com/T/#t
>
> This patchset is based on rdma/for-next branch.
Applied to for-next, thanks
> Note: I tried the patchset for fast memory registration on write path can still apply.
> https://lore.kernel.org/linux-rdma/20210608113536.42965-1-jinpu.wang@ionos.com/T/#t
Not sure how you did this, because it doesn't apply for me, it was
sent from some internal tree by the looks of it.
Jason
prev parent reply other threads:[~2021-06-18 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 9:03 [PATCHv3 for-next 0/5] Misc update for RTRS Jack Wang
2021-06-14 9:03 ` [PATCHv3 for-next 1/5] RDMA/rtrs-srv: Set minimal max_send_wr and max_recv_wr Jack Wang
2021-06-14 9:03 ` [PATCHv3 for-next 2/5] RDMA/rtrs-clt: Use minimal max_send_sge when create qp Jack Wang
2021-06-14 9:03 ` [PATCHv3 for-next 3/5] RDMA/rtrs: RDMA_RXE requires more number of WR Jack Wang
2021-06-14 9:03 ` [PATCHv3 for-next 4/5] RDMA/rtrs: Rename cq_size/queue_size to cq_num/queue_num Jack Wang
2021-06-14 9:03 ` [PATCHv3 for-next 5/5] RDMA/rtrs: Check device max_qp_wr limit when create QP Jack Wang
2021-06-18 16:51 ` Jason Gunthorpe [this message]
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=20210618165138.GA2052316@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=haris.iqbal@ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.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 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.