From: Hyong Youb Kim <hyonkim@cisco.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>,
Hyong Youb Kim <hyonkim@cisco.com>
Subject: [PATCH v3 0/3] net/enic: support VF and fix minor issues
Date: Fri, 9 Aug 2024 00:07:51 -0700 [thread overview]
Message-ID: <20240809070754.26128-1-hyonkim@cisco.com> (raw)
In-Reply-To: <20240808061433.14971-1-hyonkim@cisco.com>
This series contains minor updates for net/enic. The first patch
supports SR-IOV VF, which now requires the use of admin channel. The
other patches are not related to VF, but included here to ease review.
---
v3:
* add spdx, doc, rel_notes (Ferruh's comments)
v2:
* fix compiler warnings
Hyong Youb Kim (3):
net/enic: support SR-IOV VF using admin channel
net/enic: add speed capabilities for newer models
net/enic: allow multicast in MAC address add callback
doc/guides/nics/enic.rst | 123 ++--
doc/guides/rel_notes/release_24_11.rst | 5 +
drivers/net/enic/base/vnic_cq.c | 27 +
drivers/net/enic/base/vnic_cq.h | 3 +
drivers/net/enic/base/vnic_dev.c | 48 ++
drivers/net/enic/base/vnic_dev.h | 3 +
drivers/net/enic/base/vnic_devcmd.h | 49 ++
drivers/net/enic/base/vnic_resource.h | 32 +-
drivers/net/enic/base/vnic_rq.c | 27 +
drivers/net/enic/base/vnic_rq.h | 7 +
drivers/net/enic/base/vnic_wq.c | 37 +-
drivers/net/enic/base/vnic_wq.h | 5 +
drivers/net/enic/enic.h | 28 +-
drivers/net/enic/enic_ethdev.c | 29 +-
drivers/net/enic/enic_main.c | 97 +--
drivers/net/enic/enic_res.c | 12 +
drivers/net/enic/enic_rxtx.c | 20 +
drivers/net/enic/enic_sriov.c | 801 +++++++++++++++++++++++++
drivers/net/enic/enic_sriov.h | 211 +++++++
drivers/net/enic/meson.build | 1 +
20 files changed, 1452 insertions(+), 113 deletions(-)
create mode 100644 drivers/net/enic/enic_sriov.c
create mode 100644 drivers/net/enic/enic_sriov.h
--
2.35.2
next prev parent reply other threads:[~2024-08-09 7:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 4:18 [PATCH " Hyong Youb Kim
2024-08-08 4:18 ` [PATCH 1/3] net/enic: support SR-IOV VF using admin channel Hyong Youb Kim
2024-08-08 4:18 ` [PATCH 2/3] net/enic: add speed capabilities for newer models Hyong Youb Kim
2024-08-08 4:18 ` [PATCH 3/3] net/enic: allow multicast in MAC address add callback Hyong Youb Kim
2024-08-08 6:14 ` [PATCH v2 0/3] net/enic: support VF and fix minor issues Hyong Youb Kim
2024-08-08 6:14 ` [PATCH v2 1/3] net/enic: support SR-IOV VF using admin channel Hyong Youb Kim
2024-08-08 8:50 ` Ferruh Yigit
2024-08-09 6:27 ` Hyong Youb Kim (hyonkim)
2024-08-08 6:14 ` [PATCH v2 2/3] net/enic: add speed capabilities for newer models Hyong Youb Kim
2024-08-08 8:50 ` Ferruh Yigit
2024-08-09 6:28 ` Hyong Youb Kim (hyonkim)
2024-08-08 6:14 ` [PATCH v2 3/3] net/enic: allow multicast in MAC address add callback Hyong Youb Kim
2024-08-08 8:50 ` Ferruh Yigit
2024-08-09 6:49 ` Hyong Youb Kim (hyonkim)
2024-08-09 7:07 ` Hyong Youb Kim [this message]
2024-08-09 7:07 ` [PATCH v3 1/3] net/enic: support SR-IOV VF using admin channel Hyong Youb Kim
2024-08-09 7:07 ` [PATCH v3 2/3] net/enic: add speed capabilities for newer models Hyong Youb Kim
2024-08-09 7:07 ` [PATCH v3 3/3] net/enic: allow multicast in MAC address add callback Hyong Youb Kim
2024-09-22 4:35 ` [PATCH v3 0/3] net/enic: support VF and fix minor issues 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=20240809070754.26128-1-hyonkim@cisco.com \
--to=hyonkim@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=johndale@cisco.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).