From: Selvin Xavier <selvin.xavier@broadcom.com>
To: jgg@ziepe.ca, dledford@redhat.com
Cc: linux-rdma@vger.kernel.org, Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH for-next 0/2] RDMA/bnxt_re: Allow bigger user MRs
Date: Wed, 6 Jan 2021 22:39:17 -0800 [thread overview]
Message-ID: <1610001559-13193-1-git-send-email-selvin.xavier@broadcom.com> (raw)
Refactor user space MR code to handle bigger MRs. Removes couple of checks
that prevented the bigger MRs.
Selvin Xavier (2):
RDMA/bnxt_re: Code refactor while populating user MRs
RDMA/bnxt_re: Allow bigger MR creation
drivers/infiniband/hw/bnxt_re/ib_verbs.c | 47 ++++----------------------------
drivers/infiniband/hw/bnxt_re/qplib_sp.c | 29 +++++---------------
drivers/infiniband/hw/bnxt_re/qplib_sp.h | 2 +-
3 files changed, 14 insertions(+), 64 deletions(-)
--
2.5.5
next reply other threads:[~2021-01-07 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 6:39 Selvin Xavier [this message]
2021-01-07 6:39 ` [PATCH for-next 1/2] RDMA/bnxt_re: Code refactor while populating user MRs Selvin Xavier
2021-01-07 8:03 ` kernel test robot
2021-01-07 6:39 ` [PATCH for-next 2/2] RDMA/bnxt_re: Allow bigger MR creation Selvin Xavier
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=1610001559-13193-1-git-send-email-selvin.xavier@broadcom.com \
--to=selvin.xavier@broadcom.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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