From: Leon Romanovsky <leon@kernel.org>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH v2 for-next 0/6] RDMA/bnxt_re: driver update for supporting low latency push
Date: Wed, 26 Apr 2023 10:19:33 +0300 [thread overview]
Message-ID: <20230426071933.GL27649@unreal> (raw)
In-Reply-To: <1682450993-17711-1-git-send-email-selvin.xavier@broadcom.com>
On Tue, Apr 25, 2023 at 12:29:47PM -0700, Selvin Xavier wrote:
> The series aims to add support for Low latency push path in
> some of the bnxt devices. The low latency implementation is
> supported only for the user applications. Also, the code
> is modified to use common mmap helper functions exported
> by IB core.
>
> User library changes are getting submitted in the pull request
> https://github.com/linux-rdma/rdma-core/pull/1321
>
> Please review.
>
> Thanks,
> Selvin Xavier
>
We are in merge window now.
Thanks
prev parent reply other threads:[~2023-04-26 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 19:29 [PATCH v2 for-next 0/6] RDMA/bnxt_re: driver update for supporting low latency push Selvin Xavier
2023-04-25 19:29 ` [PATCH v2 for-next 1/6] RDMA/bnxt_re: Use the common mmap helper functions Selvin Xavier
2023-04-25 19:29 ` [PATCH v2 for-next 2/6] RDMA/bnxt_re: Add disassociate ucontext support Selvin Xavier
2023-04-25 19:29 ` [PATCH v2 for-next 3/6] RDMA/bnxt_re: Query function capabilities from firmware Selvin Xavier
2023-04-25 21:02 ` kernel test robot
2023-04-25 19:29 ` [PATCH v2 for-next 4/6] RDMA/bnxt_re: Move the interface version to chip context structure Selvin Xavier
2023-04-25 19:29 ` [PATCH v2 for-next 5/6] RDMA/bnxt_re: Reorg the bar mapping Selvin Xavier
2023-04-25 19:29 ` [PATCH v2 for-next 6/6] RDMA/bnxt_re: Enable low latency push Selvin Xavier
2023-04-26 7:19 ` Leon Romanovsky [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=20230426071933.GL27649@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
/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).