[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZHoPBYx2lZJ+i1LC@corigine.com>
Date: Fri, 2 Jun 2023 17:47:17 +0200
From: Simon Horman <simon.horman@...igine.com>
To: Amritha Nambiar <amritha.nambiar@...el.com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
sridhar.samudrala@...el.com
Subject: Re: [net-next/RFC PATCH v1 4/4] netdev-genl: Add support for
exposing napi info from netdev
On Thu, Jun 01, 2023 at 10:42:41AM -0700, Amritha Nambiar wrote:
> Add support in ynl/netdev.yaml for napi related information. The
> netdev structure tracks all the napi instances and napi fields.
> The napi instances and associated queue[s] can be retrieved this way.
>
> Refactored netdev-genl to support exposing napi<->queue[s] mapping
> that is retained in a netdev.
Hi Amritha,
This feels like it should be two patches to me.
Though it is not something I feel strongly about.
> Signed-off-by: Amritha Nambiar <amritha.nambiar@...el.com>
...
> +static int
> +netdev_nl_dev_napi_prepare_fill(struct net_device *netdev,
> + struct sk_buff **pskb, u32 portid, u32 seq,
> + int flags, u32 cmd, enum netdev_nl_type type)
> +{
> + struct nlmsghdr *nlh;
> + struct sk_buff *skb = *pskb;
> + bool last = false;
> + int index = 0;
> + void *hdr;
> + int err;
> +
nit: please use reverse xmas tree - longest line to shortest - for
local variable declarations in (new) Networking code.
...
Powered by blists - more mailing lists