From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Larysa Zaremba <larysa.zaremba@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
Mustafa Ismail <mustafa.ismail@intel.com>,
"Tatyana Nikolova" <tatyana.e.nikolova@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
"Lee Trager" <lee@trager.us>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
"Sridhar Samudrala" <sridhar.samudrala@intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
Wenjun Wu <wenjun1.wu@intel.com>,
Ahmed Zaki <ahmed.zaki@intel.com>, <netdev@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
Madhu Chittim <madhu.chittim@intel.com>,
"Josh Hay" <joshua.a.hay@intel.com>,
Milena Olech <milena.olech@intel.com>,
<pavan.kumar.linga@intel.com>,
"Singhai, Anjali" <anjali.singhai@intel.com>,
Phani R Burra <phani.r.burra@intel.com>
Subject: Re: [PATCH iwl-next 06/14] libeth: add bookkeeping support for control queue messages
Date: Tue, 15 Apr 2025 11:54:10 -0700 [thread overview]
Message-ID: <4b208c4e-10cf-48e4-b10d-6f52a25ffc07@intel.com> (raw)
In-Reply-To: <20250408124816.11584-7-larysa.zaremba@intel.com>
On 4/8/2025 5:47 AM, Larysa Zaremba wrote:
> From: Phani R Burra <phani.r.burra@intel.com>
...
> +/**
> + * struct libeth_ctlq_xn_manager - structure representing the array of virtchnl
> + * transaction entries
> + * @ctx: pointer to controlq context structure
> + * @free_xns_bm_lock: lock to protect the free Xn entries bit map
> + * @free_xns_bm: bitmap that represents the free Xn entries
> + * @ring: array of Xn entries
> + * @cookie: unique message identifier
> + */
Some kdoc issues:
> include/net/libeth/controlq.h:330: warning: Function parameter or
struct member 'can_destroy' not described in 'libeth_ctlq_xn_manager'
> include/net/libeth/controlq.h:330: warning: Function parameter or
struct member 'shutdown' not described in 'libeth_ctlq_xn_manager'
> +struct libeth_ctlq_xn_manager {
> + struct libeth_ctlq_ctx *ctx;
> + spinlock_t free_xns_bm_lock; /* get/check entries */
> + DECLARE_BITMAP(free_xns_bm, LIBETH_CTLQ_MAX_XN_ENTRIES);
> + struct libeth_ctlq_xn ring[LIBETH_CTLQ_MAX_XN_ENTRIES];
> + struct completion can_destroy;
> + bool shutdown;
> + u8 cookie;
> +};
> +
> +/**
> + * struct libeth_ctlq_xn_send_params - structure representing send Xn entry
> + * @resp_cb: callback to handle the response of an asynchronous virtchnl message
> + * @rel_tx_buf: driver entry point for freeing the send buffer after send
> + * @xnm: Xn manager to process Xn entries
> + * @ctlq: send control queue information
> + * @ctlq_msg: control queue message information
> + * @send_buf: represents the buffer that carries outgoing information
> + * @recv_mem: receive buffer
> + * @send_ctx: context for call back function
> + * @timeout_ms: virtchnl transaction timeout in msecs
> + * @chnl_opcode: virtchnl message opcode
> + */
> +struct libeth_ctlq_xn_send_params {
> + void (*resp_cb)(void *ctx, struct kvec *mem, int status);
> + void (*rel_tx_buf)(const void *buf_va);
> + struct libeth_ctlq_xn_manager *xnm;
> + struct libeth_ctlq_info *ctlq;
> + struct libeth_ctlq_msg *ctlq_msg;
> + struct kvec send_buf;
> + struct kvec recv_mem;
> + void *send_ctx;
> + u64 timeout_ms;
> + u32 chnl_opcode;
> +};
> +
> +/**
> + * libeth_cp_can_send_onstack - find if a virtchnl message can be sent using a
> + * stack variable
> + * @size: virtchnl buffer size
> + */
and here:
> include/net/libeth/controlq.h:364: warning: No description found for
return value of 'libeth_cp_can_send_onstack'
> +static inline bool libeth_cp_can_send_onstack(u32 size)
> +{
> + return size <= LIBETH_CP_TX_COPYBREAK;
> +}
> +
> +/**
> + * struct libeth_ctlq_xn_recv_params - structure representing receive Xn entry
> + * @ctlq_msg_handler: callback to handle a message originated from the peer
> + * @xnm: Xn manager to process Xn entries
> + * @ctx: pointer to context structure
> + * @ctlq: control queue information
> + */
and here:
> include/net/libeth/controlq.h:380: warning: Excess struct member
'ctx' description in 'libeth_ctlq_xn_recv_params'
Thanks,
Tony
> +struct libeth_ctlq_xn_recv_params {
> + void (*ctlq_msg_handler)(struct libeth_ctlq_ctx *ctx,
> + struct libeth_ctlq_msg *msg);
> + struct libeth_ctlq_xn_manager *xnm;
> + struct libeth_ctlq_info *ctlq;
> +};
> +
next prev parent reply other threads:[~2025-04-15 18:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 12:47 [PATCH iwl-next 00/14] Introduce iXD driver Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 01/14] virtchnl: create 'include/linux/intel' and move necessary header files Larysa Zaremba
2025-04-15 18:53 ` Tony Nguyen
2025-04-08 12:47 ` [PATCH iwl-next 02/14] virtchnl: introduce control plane version fields Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 03/14] libeth: add PCI device initialization helpers to libeth Larysa Zaremba
2025-04-21 14:08 ` Simon Horman
2025-04-08 12:47 ` [PATCH iwl-next 04/14] libeth: allow to create fill queues without NAPI Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 05/14] libeth: add control queue support Larysa Zaremba
2025-04-10 8:21 ` Leon Romanovsky
2025-04-10 10:44 ` Larysa Zaremba
2025-04-10 11:23 ` Leon Romanovsky
2025-04-10 12:58 ` Larysa Zaremba
2025-04-10 13:27 ` Leon Romanovsky
2025-04-10 13:33 ` Alexander Lobakin
2025-04-10 13:58 ` Leon Romanovsky
2025-04-10 14:04 ` Alexander Lobakin
2025-04-10 13:05 ` Alexander Lobakin
2025-04-10 13:44 ` Leon Romanovsky
2025-04-10 13:59 ` Larysa Zaremba
2025-04-11 17:18 ` Leon Romanovsky
2025-04-10 14:00 ` [Intel-wired-lan] " Alexander Lobakin
2025-04-08 12:47 ` [PATCH iwl-next 06/14] libeth: add bookkeeping support for control queue messages Larysa Zaremba
2025-04-15 18:54 ` Tony Nguyen [this message]
2025-04-21 14:19 ` Simon Horman
2025-04-08 12:47 ` [PATCH iwl-next 07/14] idpf: remove 'vport_params_reqd' field Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 08/14] idpf: refactor idpf to use libeth controlq and Xn APIs Larysa Zaremba
2025-04-21 14:25 ` Simon Horman
2025-04-08 12:47 ` [PATCH iwl-next 09/14] idpf: make mbx_task queueing and cancelling more consistent Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 10/14] idpf: print a debug message and bail in case of non-event ctlq message Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 11/14] ixd: add basic driver framework for Intel(R) Control Plane Function Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 12/14] ixd: add reset checks and initialize the mailbox Larysa Zaremba
2025-04-08 12:47 ` [PATCH iwl-next 13/14] ixd: add the core initialization Larysa Zaremba
2025-04-08 12:48 ` [PATCH iwl-next 14/14] ixd: add devlink support Larysa Zaremba
2025-04-15 18:54 ` Tony Nguyen
2025-04-16 15:49 ` [PATCH iwl-next 00/14] Introduce iXD driver Alexander Lobakin
2025-04-16 16:23 ` Keller, Jacob E
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=4b208c4e-10cf-48e4-b10d-6f52a25ffc07@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anjali.singhai@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=maddy@linux.ibm.com \
--cc=madhu.chittim@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=milena.olech@intel.com \
--cc=mpe@ellerman.id.au \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.kumar.linga@intel.com \
--cc=phani.r.burra@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=tatyana.e.nikolova@intel.com \
--cc=wenjun1.wu@intel.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