[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c6210bf9-be61-4d57-faa1-962c3a51ae87@intel.com>
Date: Tue, 8 Oct 2024 16:45:38 +0300
From: Avigail Dahan <Avigailx.dahan@...el.com>
To: Joe Damato <jdamato@...tly.com>, <netdev@...r.kernel.org>
CC: Przemek Kitszel <przemyslaw.kitszel@...el.com>, open list
<linux-kernel@...r.kernel.org>, Eric Dumazet <edumazet@...gle.com>, "Tony
Nguyen" <anthony.l.nguyen@...el.com>, "moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@...ts.osuosl.org>, Jakub Kicinski <kuba@...nel.org>, "Paolo
Abeni" <pabeni@...hat.com>, "David S. Miller" <davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [net-next v3 1/2] e1000e: Link NAPI instances
to queues and IRQs
On 30/09/2024 20:12, Joe Damato wrote:
> Add support for netdev-genl, allowing users to query IRQ, NAPI, and queue
> information.
>
> After this patch is applied, note the IRQs assigned to my NIC:
>
> $ cat /proc/interrupts | grep ens | cut -f1 --delimiter=':'
> 50
> 51
> 52
>
> While e1000e allocates 3 IRQs (RX, TX, and other), it looks like e1000e
> only has a single NAPI, so I've associated the NAPI with the RX IRQ (50
> on my system, seen above).
>
> Note the output from the cli:
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --dump napi-get --json='{"ifindex": 2}'
> [{'id': 145, 'ifindex': 2, 'irq': 50}]
>
> This device supports only 1 rx and 1 tx queue. so querying that:
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --dump queue-get --json='{"ifindex": 2}'
> [{'id': 0, 'ifindex': 2, 'napi-id': 145, 'type': 'rx'},
> {'id': 0, 'ifindex': 2, 'napi-id': 145, 'type': 'tx'}]
>
> Signed-off-by: Joe Damato <jdamato@...tly.com>
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
Tested-by: Avigail Dahan <avigailx.dahan@...el.com>
Powered by blists - more mailing lists