linux-kernel - Re: [net-next v2 1/2] gve: Map IRQs to NAPI instances

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+f9V1O5QZfbgVVpQgikgOGSP5jmTAbrOn-3oT=AEnsobg6U+w@mail.gmail.com>
Date: Tue, 1 Oct 2024 08:38:07 -0700
From: Praveen Kaligineedi <pkaligineedi@...gle.com>
To: Joe Damato <jdamato@...tly.com>
Cc: netdev@...r.kernel.org, horms@...nel.org, 
	Jeroen de Borst <jeroendb@...gle.com>, Shailend Chand <shailend@...gle.com>, 
	"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, 
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 
	Willem de Bruijn <willemb@...gle.com>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [net-next v2 1/2] gve: Map IRQs to NAPI instances

On Mon, Sep 30, 2024 at 2:07 PM Joe Damato <jdamato@...tly.com> wrote:
>
> Use netdev-genl interface to map IRQs to NAPI instances so that this
> information is accessible by user apps via netlink.
>
> $ cat /proc/interrupts | grep gve | grep -v mgmnt | cut -f1 --delimiter=':'
>  34
>  35
>  36
>  37
>  38
>  39
>  40
> [...]
>  65
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
>                          --dump napi-get --json='{"ifindex": 2}'
> [{'id': 8288, 'ifindex': 2, 'irq': 65},
>   [...]
>  {'id': 8263, 'ifindex': 2, 'irq': 40},
>  {'id': 8262, 'ifindex': 2, 'irq': 39},
>  {'id': 8261, 'ifindex': 2, 'irq': 38},
>  {'id': 8260, 'ifindex': 2, 'irq': 37},
>  {'id': 8259, 'ifindex': 2, 'irq': 36},
>  {'id': 8258, 'ifindex': 2, 'irq': 35},
>  {'id': 8257, 'ifindex': 2, 'irq': 34}]
>
> Signed-off-by: Joe Damato <jdamato@...tly.com>

Reviewed-by: Praveen Kaligineedi <pkaligineedi@...gle.com>