From: Simon Horman <horms@kernel.org>
To: Satish Kharat <satishkh@cisco.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sesidhar Baddela <sebaddel@cisco.com>,
Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH net-next v8 00/10] enic: SR-IOV V2 admin channel and MBOX protocol
Date: Fri, 12 Jun 2026 11:52:24 +0100 [thread overview]
Message-ID: <20260612105224.GE625020@horms.kernel.org> (raw)
In-Reply-To: <20260609-enic-sriov-v2-admin-channel-v2-v8-0-8ad8babbb826@cisco.com>
On Tue, Jun 09, 2026 at 09:32:26AM -0700, Satish Kharat wrote:
> This series adds the admin channel infrastructure and mailbox (MBOX)
> protocol needed for V2 SR-IOV support in the enic driver.
>
> The V2 SR-IOV design uses a direct PF-VF communication channel built on
> dedicated WQ/RQ/CQ hardware resources and an MSI-X interrupt.
>
> Firmware capability and admin channel infrastructure (patches 1-4):
> - Probe-time firmware feature check for V2 SR-IOV support
> - Admin channel open/close, RQ buffer management, CQ service
> with MSI-X interrupt and workqueue-based polling
>
> MBOX protocol and VF enable (patches 5-10):
> - MBOX message types, core send/receive, PF and VF handlers
> - V2 SR-IOV enable wiring with admin channel setup
> - V2 VF probe with admin channel and PF registration
>
> Signed-off-by: Satish Kharat <satishkh@cisco.com>
Hi Satish,
There is AI-generated review of this patch-set available on both
https://sashiko.dev and https://netdev-ai.bots.linux.dev/sashiko/
I would appreciate it if you could look over that with a view
to addressing any issues that directly affect this patch.
prev parent reply other threads:[~2026-06-12 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:32 [PATCH net-next v8 00/10] enic: SR-IOV V2 admin channel and MBOX protocol Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 01/10] enic: verify firmware supports V2 SR-IOV at probe time Satish Kharat
2026-06-09 17:30 ` Breno Leitao
2026-06-09 18:24 ` Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 02/10] enic: add admin channel open and close for SR-IOV Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 03/10] enic: add admin RQ buffer management Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 04/10] enic: add admin CQ service with MSI-X interrupt and workqueue polling Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 05/10] enic: define MBOX message types and header structures Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 06/10] enic: add MBOX core send and receive for admin channel Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 07/10] enic: add MBOX PF handlers for VF register and capability Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 08/10] enic: add MBOX VF handlers for capability, register and link state Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 09/10] enic: wire V2 SR-IOV enable with admin channel and MBOX Satish Kharat
2026-06-09 16:32 ` [PATCH net-next v8 10/10] enic: add V2 VF probe with admin channel and PF registration Satish Kharat
2026-06-12 10:52 ` Simon Horman [this message]
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=20260612105224.GE625020@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.