From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net, dledford@redhat.com, jgg@mellanox.com
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
nhorman@redhat.com, sassmann@redhat.com,
mustafa.ismail@intel.com, shiraz.saleem@intel.com,
david.m.ertman@intel.com
Subject: [net-next 0/3][pull request] Intel Wired LAN ver Updates 2019-07-03
Date: Wed, 3 Jul 2019 19:12:49 -0700 [thread overview]
Message-ID: <20190704021252.15534-1-jeffrey.t.kirsher@intel.com> (raw)
This series contains updates to i40e an ice drivers only and is required
for a series of changes being submitted to the RDMA maintainer/tree.
Vice Versa, the Intel RDMA driver patches could not be applied to
net-next due to dependencies to the changes currently in the for-next
branch of the rdma git tree. The Intel RDMA driver patches are
available in the following git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/rdma for-next
(reference only)
Dave initializes the ice driver to support RDMA by creating and
registering a platform device for the RDMA driver to register to on a
virtual bus by utilizing the platform bus to provide this access.
Followed up by operations for the peer device/driver to communicate with
each other to request resources and manage event notification.
Shiraz does the similar work in the i40e driver, while retaining the
old global register/unregister calls exported for i40iw until that
driver is removed from the kernel.
The following are changes since commit a51df9f8da43e8bf9e508143630849b7d696e053:
gve: fix -ENOMEM null check on a page allocation
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE
Shiraz Saleem (1):
i40e: Register RDMA client devices to the virtual platform bus
Tony Nguyen (2):
ice: Initialize and register platform device to provide RDMA
ice: Implement peer communications
drivers/net/ethernet/intel/i40e/i40e_client.c | 116 +-
drivers/net/ethernet/intel/i40e/i40e_client.h | 8 +
drivers/net/ethernet/intel/ice/Makefile | 1 +
drivers/net/ethernet/intel/ice/ice.h | 15 +
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 33 +
drivers/net/ethernet/intel/ice/ice_common.c | 194 +++
drivers/net/ethernet/intel/ice/ice_common.h | 9 +
drivers/net/ethernet/intel/ice/ice_dcb_lib.c | 64 +
drivers/net/ethernet/intel/ice/ice_dcb_lib.h | 2 +
.../net/ethernet/intel/ice/ice_hw_autogen.h | 1 +
drivers/net/ethernet/intel/ice/ice_idc.c | 1354 +++++++++++++++++
drivers/net/ethernet/intel/ice/ice_idc.h | 377 +++++
drivers/net/ethernet/intel/ice/ice_idc_int.h | 82 +
drivers/net/ethernet/intel/ice/ice_lib.c | 35 +-
drivers/net/ethernet/intel/ice/ice_lib.h | 2 +
drivers/net/ethernet/intel/ice/ice_main.c | 94 +-
drivers/net/ethernet/intel/ice/ice_sched.c | 69 +-
drivers/net/ethernet/intel/ice/ice_switch.c | 27 +
drivers/net/ethernet/intel/ice/ice_switch.h | 4 +
drivers/net/ethernet/intel/ice/ice_type.h | 4 +
.../net/ethernet/intel/ice/ice_virtchnl_pf.c | 25 -
21 files changed, 2462 insertions(+), 54 deletions(-)
create mode 100644 drivers/net/ethernet/intel/ice/ice_idc.c
create mode 100644 drivers/net/ethernet/intel/ice/ice_idc.h
create mode 100644 drivers/net/ethernet/intel/ice/ice_idc_int.h
--
2.21.0
next reply other threads:[~2019-07-04 2:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 2:12 Jeff Kirsher [this message]
2019-07-04 2:12 ` [net-next 1/3] ice: Initialize and register platform device to provide RDMA Jeff Kirsher
2019-07-04 12:16 ` Jason Gunthorpe
2019-07-04 12:29 ` Greg KH
2019-07-04 12:37 ` Jason Gunthorpe
2019-07-04 12:42 ` Greg KH
2019-07-04 12:48 ` Jason Gunthorpe
2019-07-04 13:46 ` Greg KH
2019-07-04 13:53 ` Jason Gunthorpe
2019-07-05 16:33 ` Saleem, Shiraz
2019-07-06 8:25 ` Greg KH
2019-07-06 16:03 ` Saleem, Shiraz
2019-07-04 2:12 ` [net-next 2/3] ice: Implement peer communications Jeff Kirsher
2019-07-04 2:12 ` [net-next 3/3] i40e: Register RDMA client devices to the virtual platform bus Jeff Kirsher
2019-07-04 12:15 ` [net-next 0/3][pull request] Intel Wired LAN ver Updates 2019-07-03 Jason Gunthorpe
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=20190704021252.15534-1-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
--cc=shiraz.saleem@intel.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).