From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, milena.olech@intel.com,
anton.nadezhdin@intel.com,
Pavan Kumar Linga <pavan.kumar.linga@intel.com>
Subject: [PATCH iwl-next v3 0/9] refactor IDPF resource access
Date: Mon, 28 Apr 2025 10:35:43 -0700 [thread overview]
Message-ID: <20250428173552.2884-1-pavan.kumar.linga@intel.com> (raw)
Queue and vector resources for a given vport, are stored in the
idpf_vport structure. At the time of configuration, these
resources are accessed using vport pointer. Meaning, all the
config path functions are tied to the default queue and vector
resources of the vport.
There are use cases which can make use of config path functions
to configure queue and vector resources that are not tied to any
vport. One such use case is PTP secondary mailbox creation
(it would be in a followup series). To configure queue and interrupt
resources for such cases, we can make use of the existing config
infrastructure by passing the necessary queue and vector resources info.
To achieve this, group the existing queue and vector resources into
default resource group and refactor the code to pass the resource
pointer to the config path functions.
This series also includes patches which generalizes the send virtchnl
message APIs and mailbox API that are necessary for the implementation
of PTP secondary mailbox.
---
v3:
* rebase on top of libeth XDP and other patches
v2:
* rebase on top of PTP patch series
Pavan Kumar Linga (9):
idpf: introduce local idpf structure to store virtchnl queue chunks
idpf: use existing queue chunk info instead of preparing it
idpf: introduce idpf_q_vec_rsrc struct and move vector resources to it
idpf: move queue resources to idpf_q_vec_rsrc structure
idpf: reshuffle idpf_vport struct members to avoid holes
idpf: add rss_data field to RSS function parameters
idpf: generalize send virtchnl message API
idpf: avoid calling get_rx_ptypes for each vport
idpf: generalize mailbox API
drivers/net/ethernet/intel/idpf/idpf.h | 152 ++-
drivers/net/ethernet/intel/idpf/idpf_dev.c | 12 +-
.../net/ethernet/intel/idpf/idpf_ethtool.c | 87 +-
drivers/net/ethernet/intel/idpf/idpf_lib.c | 233 ++--
drivers/net/ethernet/intel/idpf/idpf_ptp.c | 17 +-
drivers/net/ethernet/intel/idpf/idpf_txrx.c | 639 +++++-----
drivers/net/ethernet/intel/idpf/idpf_txrx.h | 36 +-
drivers/net/ethernet/intel/idpf/idpf_vf_dev.c | 15 +-
.../net/ethernet/intel/idpf/idpf_virtchnl.c | 1130 ++++++++---------
.../net/ethernet/intel/idpf/idpf_virtchnl.h | 81 +-
10 files changed, 1252 insertions(+), 1150 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-28 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 17:35 Pavan Kumar Linga [this message]
2025-04-28 17:35 ` [PATCH iwl-next v3 1/9] idpf: introduce local idpf structure to store virtchnl queue chunks Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 2/9] idpf: use existing queue chunk info instead of preparing it Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 3/9] idpf: introduce idpf_q_vec_rsrc struct and move vector resources to it Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 4/9] idpf: move queue resources to idpf_q_vec_rsrc structure Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 5/9] idpf: reshuffle idpf_vport struct members to avoid holes Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 6/9] idpf: add rss_data field to RSS function parameters Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 7/9] idpf: generalize send virtchnl message API Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 8/9] idpf: avoid calling get_rx_ptypes for each vport Pavan Kumar Linga
2025-04-28 17:35 ` [PATCH iwl-next v3 9/9] idpf: generalize mailbox API Pavan Kumar Linga
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=20250428173552.2884-1-pavan.kumar.linga@intel.com \
--to=pavan.kumar.linga@intel.com \
--cc=anton.nadezhdin@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.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 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).