From: Leon Romanovsky <leon@kernel.org>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: andrew.gospodarek@broadcom.com, davem@davemloft.net,
edumazet@google.com, jgg@ziepe.ca, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
michael.chan@broadcom.com, netdev@vger.kernel.org,
pabeni@redhat.com, selvin.xavier@broadcom.com
Subject: Re: [PATCH 0/8] Add Auxiliary driver support
Date: Tue, 10 Jan 2023 10:38:47 +0200 [thread overview]
Message-ID: <Y70kF3cpyogrxUUC@unreal> (raw)
In-Reply-To: <20230108030208.26390-1-ajit.khaparde@broadcom.com>
On Sat, Jan 07, 2023 at 07:02:00PM -0800, Ajit Khaparde wrote:
>
> Ajit Khaparde <ajit.khaparde@broadcom.com>
> Dec 7, 2022, 9:53 AM
> to me, andrew.gospodarek, davem, edumazet, jgg, kuba, leon, linux-kernel, linux-rdma, michael.chan, netdev, pabeni, selvin.xavier
>
> Add auxiliary device driver for Broadcom devices.
> The bnxt_en driver will register and initialize an aux device
> if RDMA is enabled in the underlying device.
> The bnxt_re driver will then probe and initialize the
> RoCE interfaces with the infiniband stack.
>
> We got rid of the bnxt_en_ops which the bnxt_re driver used to
> communicate with bnxt_en.
> Similarly We have tried to clean up most of the bnxt_ulp_ops.
> In most of the cases we used the functions and entry points provided
> by the auxiliary bus driver framework.
> And now these are the minimal functions needed to support the functionality.
>
> We will try to work on getting rid of the remaining if we find any
> other viable option in future.
>
> v1->v2:
> - Incorporated review comments including usage of ulp_id &
> complex function indirections.
> - Used function calls provided by the auxiliary bus interface
> instead of proprietary calls.
> - Refactor code to remove ROCE driver's access to bnxt structure.
>
> v2->v3:
> - Addressed review comments including cleanup of some unnecessary wrappers
> - Fixed warnings seen during cross compilation
>
> v3->v4:
> - Cleaned up bnxt_ulp.c and bnxt_ulp.h further
> - Removed some more dead code
> - Sending the patchset as a standalone series
>
> v4->v5:
> - Removed the SRIOV config callback which bnxt_en driver was calling into
> bnxt_re driver.
> - Removed excessive checks for rdev and other pointers.
>
> v5->v6:
> - Removed excessive checks for dev and other pointers
> - Remove runtime interrupt vector allocation. bnxt_en preallocates
> interrupt vectors for bnxt_re to use.
>
> Please apply. Thanks.
>
> Ajit Khaparde (7):
> bnxt_en: Add auxiliary driver support
> RDMA/bnxt_re: Use auxiliary driver interface
> bnxt_en: Remove usage of ulp_id
> bnxt_en: Use direct API instead of indirection
> bnxt_en: Use auxiliary bus calls over proprietary calls
> RDMA/bnxt_re: Remove the sriov config callback
> bnxt_en: Remove runtime interrupt vector allocation
>
> Hongguang Gao (1):
> bnxt_en: Remove struct bnxt access from RoCE driver
>
Thanks a lot for pursuing it,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
prev parent reply other threads:[~2023-01-10 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 3:02 [PATCH 0/8] Add Auxiliary driver support Ajit Khaparde
2023-01-08 3:02 ` [PATCH 1/8] bnxt_en: Add auxiliary " Ajit Khaparde
2023-01-10 22:51 ` Jakub Kicinski
2023-01-10 23:49 ` Ajit Khaparde
2023-01-12 19:08 ` kernel test robot
2023-01-08 3:02 ` [PATCH 2/8] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2023-01-08 3:02 ` [PATCH 3/8] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2023-01-08 3:02 ` [PATCH 4/8] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2023-01-08 3:02 ` [PATCH 5/8] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2023-01-08 3:02 ` [PATCH 6/8] bnxt_en: Remove struct bnxt access from RoCE driver Ajit Khaparde
2023-01-08 3:02 ` [PATCH 7/8] RDMA/bnxt_re: Remove the sriov config callback Ajit Khaparde
2023-01-08 3:02 ` [PATCH 8/8] bnxt_en: Remove runtime interrupt vector allocation Ajit Khaparde
2023-01-10 8:38 ` 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=Y70kF3cpyogrxUUC@unreal \
--to=leon@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).