[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878quhgxel.fsf@intel.com>
Date: Mon, 21 Oct 2024 10:48:18 -0700
From: Vinicius Costa Gomes <vinicius.gomes@...el.com>
To: Joe Damato <jdamato@...tly.com>, netdev@...r.kernel.org
Cc: kurt@...utronix.de, Joe Damato <jdamato@...tly.com>, Tony Nguyen
<anthony.l.nguyen@...el.com>, Przemek Kitszel
<przemyslaw.kitszel@...el.com>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, "moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@...ts.osuosl.org>, open list
<linux-kernel@...r.kernel.org>
Subject: Re: [net-next v3 1/2] igc: Link IRQs to NAPI instances
Joe Damato <jdamato@...tly.com> writes:
> Link IRQs to NAPI instances via netdev-genl API so that users can query
> this information with netlink.
>
> Compare the output of /proc/interrupts (noting that IRQ 144 is the
> "other" IRQ which does not appear to have a NAPI instance):
>
> $ cat /proc/interrupts | grep enp86s0 | cut --delimiter=":" -f1
> 128
> 129
> 130
> 131
> 132
>
> The output from netlink shows the mapping of NAPI IDs to IRQs (again
> noting that 144 is absent as it is the "other" IRQ):
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --dump napi-get --json='{"ifindex": 2}'
>
> [{'defer-hard-irqs': 0,
> 'gro-flush-timeout': 0,
> 'id': 8196,
> 'ifindex': 2,
> 'irq': 132},
> {'defer-hard-irqs': 0,
> 'gro-flush-timeout': 0,
> 'id': 8195,
> 'ifindex': 2,
> 'irq': 131},
> {'defer-hard-irqs': 0,
> 'gro-flush-timeout': 0,
> 'id': 8194,
> 'ifindex': 2,
> 'irq': 130},
> {'defer-hard-irqs': 0,
> 'gro-flush-timeout': 0,
> 'id': 8193,
> 'ifindex': 2,
> 'irq': 129}]
>
> Signed-off-by: Joe Damato <jdamato@...tly.com>
> ---
Acked-by: Vinicius Costa Gomes <vinicius.gomes@...el.com>
Cheers,
--
Vinicius
Powered by blists - more mailing lists