From: Jakub Kicinski <kuba@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>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sesidhar Baddela <sebaddel@cisco.com>
Subject: Re: [PATCH net-next v7 04/10] enic: add admin CQ service with MSI-X interrupt and NAPI polling
Date: Mon, 18 May 2026 18:36:52 -0700 [thread overview]
Message-ID: <20260518183652.388a60b1@kernel.org> (raw)
In-Reply-To: <20260513-enic-sriov-v2-admin-channel-v2-v7-4-68b9f4141f4c@cisco.com>
On Wed, 13 May 2026 08:15:41 -0700 Satish Kharat wrote:
> @@ -296,6 +296,14 @@ struct enic {
> struct vnic_rq admin_rq;
> struct vnic_cq admin_cq[2];
> struct vnic_intr admin_intr;
> + struct napi_struct admin_napi;
please do not use NAPI for FW communication channels
NAPI is for packet processing, you can use a work/tasklet
for what you're doing
> + unsigned int admin_intr_index;
> + struct work_struct admin_msg_work;
> + spinlock_t admin_msg_lock; /* protects admin_msg_list */
> + struct list_head admin_msg_list;
> + u64 admin_msg_drop_cnt;
> + void (*admin_rq_handler)(struct enic *enic, void *buf,
> + unsigned int len);
> };
> +unsigned int enic_admin_wq_cq_service(struct enic *enic)
> +{
> + struct vnic_cq *cq = &enic->admin_cq[0];
> + unsigned int work = 0;
> + void *desc;
> +
> + desc = vnic_cq_to_clean(cq);
> + while (enic_admin_cq_color(desc, cq->ring.desc_size) !=
> + cq->last_color) {
> + /* Ensure color bit is read before descriptor fields */
> + rmb();
AI review points out that this barrier is pointless or the comment
is wrong - nothing reads desc in the loop after this point.
> + vnic_cq_inc_to_clean(cq);
> + work++;
> + desc = vnic_cq_to_clean(cq);
> + }
> +
> + return work;
--
pw-bot: cr
next prev parent reply other threads:[~2026-05-19 1:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 15:15 [PATCH net-next v7 00/10] enic: SR-IOV V2 admin channel and MBOX protocol Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 01/10] enic: verify firmware supports V2 SR-IOV at probe time Satish Kharat
2026-05-14 9:13 ` Breno Leitao
2026-05-13 15:15 ` [PATCH net-next v7 02/10] enic: add admin channel open and close for SR-IOV Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 03/10] enic: add admin RQ buffer management Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 04/10] enic: add admin CQ service with MSI-X interrupt and NAPI polling Satish Kharat
2026-05-19 1:36 ` Jakub Kicinski [this message]
2026-05-13 15:15 ` [PATCH net-next v7 05/10] enic: define MBOX message types and header structures Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 06/10] enic: add MBOX core send and receive for admin channel Satish Kharat
2026-05-19 1:38 ` Jakub Kicinski
2026-05-13 15:15 ` [PATCH net-next v7 07/10] enic: add MBOX PF handlers for VF register and capability Satish Kharat
2026-05-19 1:42 ` Jakub Kicinski
2026-05-13 15:15 ` [PATCH net-next v7 08/10] enic: add MBOX VF handlers for capability, register and link state Satish Kharat
2026-05-19 1:42 ` Jakub Kicinski
2026-05-13 15:15 ` [PATCH net-next v7 09/10] enic: wire V2 SR-IOV enable with admin channel and MBOX Satish Kharat
2026-05-13 15:15 ` [PATCH net-next v7 10/10] enic: add V2 VF probe with admin channel and PF registration Satish Kharat
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=20260518183652.388a60b1@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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.