public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
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, axboe@kernel.dk, haris.iqbal@ionos.com
Subject: Re: [PATCH resend for-next 0/5] RTRS enable write path fast memory regitration
Date: Mon, 21 Jun 2021 21:03:28 -0300	[thread overview]
Message-ID: <20210622000328.GA2381534@nvidia.com> (raw)
In-Reply-To: <20210621055340.11789-1-jinpu.wang@ionos.com>

On Mon, Jun 21, 2021 at 07:53:35AM +0200, Jack Wang wrote:
> Hi Jason, hi Doug, hi Jens
> 
> Please consider to include following changes to the next merge window.
> 
> This enables fast memory registration for write IO patch, so rtrs can
> support bigger IO than 116k without splitting. With this in place, both
> read/write request are more symmetric, and we can also reduce the memory
> usage.
> 
> The patchset is orgnized as:
> - patch1 preparation.
> - patch2 implement fast memory registration for write patch.
> - patch3 reduce memory usage.
> - patch4 raise MAX_SGEMENTs
> - patch5 rnbd-clt to query and use the max_sgements setting.
> 
> As the main change is in RTRS, so it's easier to go through RDMA tree, hence
> send this patchset to linux-rdma.
> 
> This is a rebased on the top latest rdma/wip/jgg-for-next commit
> 7e78dd816e45 ("RDMA/hns: Clear extended doorbell info before using")
> 
> v1: https://lore.kernel.org/linux-rdma/20210608113536.42965-1-jinpu.wang@ionos.com/T/#t
> 
> Thanks!
> 
> Jack Wang (5):
>   RDMA/rtrs: Introduce head/tail wr
>   RDMA/rtrs-clt: Write path fast memory registration
>   RDMA/rtrs_clt: Alloc less memory with write path fast memory
>     registration
>   RDMA/rtrs-clt: Raise MAX_SEGMENTS
>   rnbd/rtrs-clt: Query and use max_segments from rtrs-clt.

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2021-06-22  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21  5:53 [PATCH resend for-next 0/5] RTRS enable write path fast memory regitration Jack Wang
2021-06-21  5:53 ` [PATCH resend for-next 1/5] RDMA/rtrs: Introduce head/tail wr Jack Wang
2021-06-21  5:53 ` [PATCH resend for-next 2/5] RDMA/rtrs-clt: Write path fast memory registration Jack Wang
2021-06-21  5:53 ` [PATCH resend for-next 3/5] RDMA/rtrs_clt: Alloc less memory with write " Jack Wang
2021-06-21  5:53 ` [PATCH resend for-next 4/5] RDMA/rtrs-clt: Raise MAX_SEGMENTS Jack Wang
2021-06-21  5:53 ` [PATCH resend for-next 5/5] rnbd/rtrs-clt: Query and use max_segments from rtrs-clt Jack Wang
2021-06-22  0:03 ` 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=20210622000328.GA2381534@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=axboe@kernel.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox