From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: mustafa.ismail@intel.com, benjamin.mikailenko@intel.com,
jesse.brandeburg@intel.com, leszek.kaliszczuk@intel.com,
przemyslaw.kitszel@intel.com, shiraz.saleem@intel.com
Subject: [Intel-wired-lan] [PATCH net-next v3 00/10] implement devlink reload in ice
Date: Wed, 21 Dec 2022 12:38:12 +0100 [thread overview]
Message-ID: <20221221113822.12858-1-michal.swiatkowski@linux.intel.com> (raw)
Hi,
This is a part of changes done in patchset [0]. Resource management is
kind of controversial part, so I split it into two patchsets.
It is the first one, covering refactor and implement reload API call.
The refactor will unblock some of the patches needed by SIOV or
subfunction.
Most of this patchset is about implementing driver reload mechanism.
Part of code from probe and rebuild is used to not duplicate code.
To allow this reuse probe and rebuild path are split into smaller
functions.
Patch "ice: split ice_vsi_setup into smaller functions" changes
boolean variable in function call to integer and adds define
for it. Instead of having the function called with true/false now it
can be called with readable defines ICE_VSI_FLAG_INIT or
ICE_VSI_FLAG_NO_INIT. It was suggested by Jacob Keller and probably this
mechanism will be implemented across ice driver in follow up patchset.
Previously the code was reviewed here [0].
[0] https://lore.kernel.org/netdev/Y3ckRWtAtZU1BdXm@unreal/T/#m3bb8feba0a62f9b4cd54cd94917b7e2143fc2ecd
I did basic tests:
* devlink reinit without a traffic
* devlink reinit when there is a traffic
* devlink reinit when some features are on (like switchdev, VFs etc.)
-> reinit is blocked
* check KASAN output while do the tests
v2 --> v3:
* there was another crash, this time in rmmod (apologize for that) ->
cleanup remove path
* KASAN found that there was memory leak because calling setting cpu rx
map twice, fix it by calling it only in VSI config path
v1 --> v2:
* fix crash caused by merger error with VSI statistic
Jacob Keller (1):
ice: stop hard coding the ICE_VSI_CTRL location
Michal Swiatkowski (9):
ice: move RDMA init to ice_idc.c
ice: alloc id for RDMA using xa_array
ice: cleanup in VSI config/deconfig code
ice: split ice_vsi_setup into smaller functions
ice: split probe into smaller functions
ice: sync netdev filters after clearing VSI
ice: move VSI delete outside deconfig
ice: update VSI instead of init in some case
ice: implement devlink reinit action
drivers/net/ethernet/intel/ice/ice.h | 6 +-
drivers/net/ethernet/intel/ice/ice_common.c | 11 +-
drivers/net/ethernet/intel/ice/ice_devlink.c | 103 +-
drivers/net/ethernet/intel/ice/ice_ethtool.c | 2 +-
drivers/net/ethernet/intel/ice/ice_fltr.c | 5 +
drivers/net/ethernet/intel/ice/ice_idc.c | 53 +-
drivers/net/ethernet/intel/ice/ice_lib.c | 1047 ++++++++---------
drivers/net/ethernet/intel/ice/ice_lib.h | 8 +-
drivers/net/ethernet/intel/ice/ice_main.c | 1090 ++++++++++--------
drivers/net/ethernet/intel/ice/ice_vf_lib.c | 2 +-
10 files changed, 1253 insertions(+), 1074 deletions(-)
--
2.36.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-12-21 11:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 11:38 Michal Swiatkowski [this message]
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 01/10] ice: move RDMA init to ice_idc.c Michal Swiatkowski
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 02/10] ice: alloc id for RDMA using xa_array Michal Swiatkowski
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 03/10] ice: cleanup in VSI config/deconfig code Michal Swiatkowski
2023-01-06 6:31 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 04/10] ice: split ice_vsi_setup into smaller functions Michal Swiatkowski
2023-01-06 6:32 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 05/10] ice: stop hard coding the ICE_VSI_CTRL location Michal Swiatkowski
2023-01-06 6:33 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 06/10] ice: split probe into smaller functions Michal Swiatkowski
2023-01-06 6:34 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 07/10] ice: sync netdev filters after clearing VSI Michal Swiatkowski
2023-01-06 6:35 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 08/10] ice: move VSI delete outside deconfig Michal Swiatkowski
2023-01-06 6:36 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 09/10] ice: update VSI instead of init in some case Michal Swiatkowski
2023-01-06 6:36 ` G, GurucharanX
2022-12-21 11:38 ` [Intel-wired-lan] [PATCH net-next v3 10/10] ice: implement devlink reinit action Michal Swiatkowski
2023-01-06 6:37 ` G, GurucharanX
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=20221221113822.12858-1-michal.swiatkowski@linux.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=benjamin.mikailenko@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leszek.kaliszczuk@intel.com \
--cc=mustafa.ismail@intel.com \
--cc=przemyslaw.kitszel@intel.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