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, niklas.soderlund@corigine.com,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 00/13] Sync the kernel driver logic
Date: Mon, 10 Apr 2023 19:00:02 +0800	[thread overview]
Message-ID: <20230410110015.2973660-1-chaoyong.he@corigine.com> (raw)

The DPDK NFP PMD share the same underlying data structure and API with
the NFP kernel driver, because they use the same firmware.

The DPDK NFP PMD only has a very initial version and not changed for a
long time, but the NFP kernel driver keeps evolve at the same time, so
the differece between them are keeping expand.

This patch series try to sync the needed logics to narrow the gap.

Chaoyong He (13):
  net/nfp: define correct size for configuration BAR
  net/nfp: move shared target logic to own source file
  net/nfp: remove the redundant macro about CPP target
  net/nfp: drop usage of return error helpers
  net/nfp: use generic macros for array size and to set bits
  net/nfp: remove dead code related to CPP
  net/nfp: remove duplicated nffw defines
  net/nfp: move NFD3 logic to own source file
  net/nfp: adjust the coding style for NFD3
  net/nfp: rename macro name of NFD3 Tx descriptor
  net/nfp: move NFDk logic to own source file
  net/nfp: adjust the coding style for NFDk
  net/nfp: modify the logic of some NFDk function

 drivers/net/nfp/flower/nfp_flower.c           |   9 +-
 drivers/net/nfp/flower/nfp_flower_ctrl.c      |   3 +-
 .../net/nfp/flower/nfp_flower_representor.c   |   1 +
 drivers/net/nfp/meson.build                   |   3 +
 drivers/net/nfp/nfd3/nfp_nfd3.h               | 161 +++
 drivers/net/nfp/nfd3/nfp_nfd3_dp.c            | 343 ++++++
 drivers/net/nfp/nfdk/nfp_nfdk.h               | 239 +++++
 drivers/net/nfp/nfdk/nfp_nfdk_dp.c            | 437 ++++++++
 drivers/net/nfp/nfp_common.c                  |   6 +-
 drivers/net/nfp/nfp_cpp_bridge.c              |   5 +-
 drivers/net/nfp/nfp_ctrl.h                    |   7 +-
 drivers/net/nfp/nfp_ethdev.c                  |   5 +-
 drivers/net/nfp/nfp_ethdev_vf.c               |   2 +
 drivers/net/nfp/nfp_rxtx.c                    | 844 +--------------
 drivers/net/nfp/nfp_rxtx.h                    | 208 +---
 .../net/nfp/nfpcore/nfp-common/nfp_cppat.h    | 725 -------------
 .../net/nfp/nfpcore/nfp-common/nfp_platform.h |  35 -
 .../net/nfp/nfpcore/nfp-common/nfp_resid.h    | 592 -----------
 drivers/net/nfp/nfpcore/nfp6000/nfp6000.h     |  20 +
 drivers/net/nfp/nfpcore/nfp_cpp.h             | 155 ++-
 drivers/net/nfp/nfpcore/nfp_cpp_pcie_ops.c    |   3 +-
 drivers/net/nfp/nfpcore/nfp_cppcore.c         |  47 +-
 drivers/net/nfp/nfpcore/nfp_hwinfo.h          |   2 +-
 drivers/net/nfp/nfpcore/nfp_mutex.c           |  39 +-
 drivers/net/nfp/nfpcore/nfp_nffw.c            |   8 +-
 drivers/net/nfp/nfpcore/nfp_nffw.h            |  10 -
 drivers/net/nfp/nfpcore/nfp_nsp.c             |   2 +-
 drivers/net/nfp/nfpcore/nfp_nsp.h             |  12 +-
 drivers/net/nfp/nfpcore/nfp_nsp_cmds.c        |   2 +-
 drivers/net/nfp/nfpcore/nfp_nsp_eth.c         |  34 +-
 drivers/net/nfp/nfpcore/nfp_resource.c        |   2 +-
 drivers/net/nfp/nfpcore/nfp_target.c          | 994 ++++++++++++++++++
 drivers/net/nfp/nfpcore/nfp_target.h          |   3 -
 33 files changed, 2417 insertions(+), 2541 deletions(-)
 create mode 100644 drivers/net/nfp/nfd3/nfp_nfd3.h
 create mode 100644 drivers/net/nfp/nfd3/nfp_nfd3_dp.c
 create mode 100644 drivers/net/nfp/nfdk/nfp_nfdk.h
 create mode 100644 drivers/net/nfp/nfdk/nfp_nfdk_dp.c
 delete mode 100644 drivers/net/nfp/nfpcore/nfp-common/nfp_cppat.h
 delete mode 100644 drivers/net/nfp/nfpcore/nfp-common/nfp_platform.h
 delete mode 100644 drivers/net/nfp/nfpcore/nfp-common/nfp_resid.h
 create mode 100644 drivers/net/nfp/nfpcore/nfp_target.c

-- 
2.39.1


             reply	other threads:[~2023-04-10 11:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 11:00 Chaoyong He [this message]
2023-04-10 11:00 ` [PATCH 01/13] net/nfp: define correct size for configuration BAR Chaoyong He
2023-04-10 11:00 ` [PATCH 02/13] net/nfp: move shared target logic to own source file Chaoyong He
2023-04-10 11:00 ` [PATCH 03/13] net/nfp: remove the redundant macro about CPP target Chaoyong He
2023-04-10 11:00 ` [PATCH 04/13] net/nfp: drop usage of return error helpers Chaoyong He
2023-04-10 11:00 ` [PATCH 05/13] net/nfp: use generic macros for array size and to set bits Chaoyong He
2023-04-10 11:00 ` [PATCH 06/13] net/nfp: remove dead code related to CPP Chaoyong He
2023-04-10 11:00 ` [PATCH 07/13] net/nfp: remove duplicated nffw defines Chaoyong He
2023-04-10 11:00 ` [PATCH 08/13] net/nfp: move NFD3 logic to own source file Chaoyong He
2023-04-10 11:00 ` [PATCH 09/13] net/nfp: adjust the coding style for NFD3 Chaoyong He
2023-04-10 11:00 ` [PATCH 10/13] net/nfp: rename macro name of NFD3 Tx descriptor Chaoyong He
2023-04-10 11:00 ` [PATCH 11/13] net/nfp: move NFDk logic to own source file Chaoyong He
2023-04-10 11:00 ` [PATCH 12/13] net/nfp: adjust the coding style for NFDk Chaoyong He
2023-04-10 11:00 ` [PATCH 13/13] net/nfp: modify the logic of some NFDk function Chaoyong He
2023-05-11 14:47 ` [PATCH 00/13] Sync the kernel driver logic Niklas Söderlund
2023-05-12 14:37 ` 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=20230410110015.2973660-1-chaoyong.he@corigine.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.com \
    --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).