From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Joe Damato <jdamato@fastly.com>, netdev@vger.kernel.org
Cc: kurt@linutronix.de, Joe Damato <jdamato@fastly.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [net-next v3 1/2] igc: Link IRQs to NAPI instances
Date: Mon, 21 Oct 2024 10:48:18 -0700 [thread overview]
Message-ID: <878quhgxel.fsf@intel.com> (raw)
In-Reply-To: <20241018171343.314835-2-jdamato@fastly.com>
Joe Damato <jdamato@fastly.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@fastly.com>
> ---
Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cheers,
--
Vinicius
next prev parent reply other threads:[~2024-10-21 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 17:13 [net-next v3 0/2] igc: Link IRQs and queues to NAPIs Joe Damato
2024-10-18 17:13 ` [net-next v3 1/2] igc: Link IRQs to NAPI instances Joe Damato
2024-10-21 17:48 ` Vinicius Costa Gomes [this message]
2024-10-22 18:50 ` Jacob Keller
2024-10-22 19:54 ` Joe Damato
2024-10-18 17:13 ` [net-next v3 2/2] igc: Link queues " Joe Damato
2024-10-21 17:48 ` Vinicius Costa Gomes
2024-10-22 20:28 ` Joe Damato
2024-10-22 20:53 ` Jacob Keller
2024-10-22 20:58 ` Joe Damato
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=878quhgxel.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@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;
as well as URLs for NNTP newsgroup(s).