From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 2/2] i40e: Register a virtbus device to provide RDMA
Date: Thu, 5 Mar 2020 22:35:25 +0000 [thread overview]
Message-ID: <1af6ad8f2d2a4b9f8041989f805a910b@intel.com> (raw)
In-Reply-To: <20200302165154.1098-2-shiraz.saleem@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Shiraz Saleem
> Sent: Monday, March 2, 2020 8:52 AM
> To: intel-wired-lan at lists.osuosl.org
> Cc: Saleem, Shiraz <shiraz.saleem@intel.com>
> Subject: [Intel-wired-lan] [PATCH 2/2] i40e: Register a virtbus device to
> provide RDMA
>
> Register client virtbus device on the virtbus for the RDMA virtbus driver
> (irdma) to bind to. It allows to realize a single RDMA driver capable of working
> with multiple netdev drivers over multi-generation Intel HW supporting
> RDMA.
> There is also no load ordering dependencies between i40e and irdma.
>
> Summary of changes:
> * Support to add/remove virtbus devices
> * Add 2 new client ops.
> * i40e_client_device_register() which is called during RDMA
> probe() per PF. Validate client drv OPs and schedule service
> task to call open()
> * i40e_client_device_unregister() called during RDMA remove()
> per PF. Call client close() and release_qvlist.
> * The global register/unregister calls exported for i40iw are retained
> until i40iw is removed from the kernel.
>
> Signed-off-by: Mustafa Ismail <mustafa.ismail@intel.com>
> Signed-off-by: Shiraz Saleem <shiraz.saleem@intel.com>
> ---
> drivers/net/ethernet/intel/Kconfig | 1 +
> drivers/net/ethernet/intel/i40e/i40e_client.c | 131
> ++++++++++++++++++++++----
> include/linux/net/intel/i40e_client.h | 15 +++
> 3 files changed, 127 insertions(+), 20 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
next prev parent reply other threads:[~2020-03-05 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 16:51 [Intel-wired-lan] [PATCH 1/2] i40e: Move client header location Shiraz Saleem
2020-03-02 16:51 ` [Intel-wired-lan] [PATCH 2/2] i40e: Register a virtbus device to provide RDMA Shiraz Saleem
2020-03-03 2:02 ` kbuild test robot
2020-03-05 22:35 ` Bowers, AndrewX [this message]
2020-03-05 22:35 ` [Intel-wired-lan] [PATCH 1/2] i40e: Move client header location Bowers, AndrewX
-- strict thread matches above, loose matches on Subject: below --
2020-01-16 23:06 Shiraz Saleem
2020-01-16 23:06 ` [Intel-wired-lan] [PATCH 2/2] i40e: Register a virtbus device to provide RDMA Shiraz Saleem
2020-01-17 22:02 ` Bowers, AndrewX
2020-01-18 2:32 ` kbuild test robot
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=1af6ad8f2d2a4b9f8041989f805a910b@intel.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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.