DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 00/11] Add the support of multiple PF
Date: Thu,  2 Nov 2023 10:23:10 +0800	[thread overview]
Message-ID: <20231102022321.2254224-1-chaoyong.he@corigine.com> (raw)

Up to now, the NFP card using only one PF (or BDF) for multiple physical
ports, this force the PMD import the difference logic for 'PF' and
'physical port'. Which is not easy to understand and also not compatible
with some DPDK applications.
This patch series add the support of multiple PF, which will remove this
complexity by make sure one 'PF' for one 'physical port' with the help of
firmware.

Chaoyong He (1):
  net/nfp: refactor the probe logic of the secondary process

Peng Zhang (9):
  net/nfp: fix the failure to initialize the LSC mask
  net/nfp: add flag to indicate multiple PFs support
  net/nfp: add major version to nsp commands
  net/nfp: adjust physical port check for multiple PFs
  net/nfp: add the check about the firmware load
  net/nfp: add PF ID used to format symbols
  net/nfp: add nsp command to check if firmware is loaded
  net/nfp: introduce keepalive mechanism for multiple PF
  drivers: enable multiple PF in application firmware

Shihong Wang (1):
  net/nfp: fix the DMA error caused by app exit abnormally

 drivers/common/nfp/nfp_common_ctrl.h   |   1 +
 drivers/net/nfp/flower/nfp_flower.c    |   4 +-
 drivers/net/nfp/flower/nfp_flower.h    |   2 +-
 drivers/net/nfp/nfp_ethdev.c           | 460 ++++++++++++++++++++++---
 drivers/net/nfp/nfp_ethdev_vf.c        |   2 +
 drivers/net/nfp/nfp_net_common.c       |   2 +-
 drivers/net/nfp/nfp_net_common.h       |  28 ++
 drivers/net/nfp/nfpcore/nfp_nsp.c      |  24 +-
 drivers/net/nfp/nfpcore/nfp_nsp.h      |   1 +
 drivers/net/nfp/nfpcore/nfp_resource.h |   3 +
 10 files changed, 464 insertions(+), 63 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-11-02  2:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  2:23 Chaoyong He [this message]
2023-11-02  2:23 ` [PATCH 01/11] net/nfp: refactor the probe logic of the secondary process Chaoyong He
2023-11-02  2:23 ` [PATCH 02/11] net/nfp: fix the failure to initialize the LSC mask Chaoyong He
2023-11-02  2:23 ` [PATCH 03/11] net/nfp: fix the DMA error caused by app exit abnormally Chaoyong He
2023-11-02  2:23 ` [PATCH 04/11] net/nfp: add flag to indicate multiple PFs support Chaoyong He
2023-11-02  2:23 ` [PATCH 05/11] net/nfp: add major version to nsp commands Chaoyong He
2023-11-02  2:23 ` [PATCH 06/11] net/nfp: adjust physical port check for multiple PFs Chaoyong He
2023-11-02  2:23 ` [PATCH 07/11] net/nfp: add the check about the firmware load Chaoyong He
2023-11-02  2:23 ` [PATCH 08/11] net/nfp: add PF ID used to format symbols Chaoyong He
2023-11-02  2:23 ` [PATCH 09/11] net/nfp: add nsp command to check if firmware is loaded Chaoyong He
2023-11-02  2:23 ` [PATCH 10/11] net/nfp: introduce keepalive mechanism for multiple PF Chaoyong He
2023-11-02  2:23 ` [PATCH 11/11] drivers: enable multiple PF in application firmware Chaoyong He
2023-11-02 14:52 ` [PATCH 00/11] Add the support of multiple PF Ferruh Yigit

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=20231102022321.2254224-1-chaoyong.he@corigine.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=oss-drivers@corigine.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).