Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lifshits, Vitaly" <vitaly.lifshits@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [net-next v3 1/2] igc: Link IRQs to NAPI instances
Date: Tue, 22 Oct 2024 10:05:44 +0300	[thread overview]
Message-ID: <72483651-72ca-48b3-9726-b3acc1873bb8@intel.com> (raw)
In-Reply-To: <878quhgxel.fsf@intel.com>



On 10/21/2024 8:48 PM, Vinicius Costa Gomes wrote:
> 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>

Reviewed-by: Vitaly Lifshits <vitaly.lifshits@intel.com>

> 
> 
> Cheers,


  reply	other threads:[~2024-10-22  7:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 17:13 [Intel-wired-lan] [net-next v3 0/2] igc: Link IRQs and queues to NAPIs Joe Damato
2024-10-18 17:13 ` [Intel-wired-lan] [net-next v3 1/2] igc: Link IRQs to NAPI instances Joe Damato
2024-10-21 17:48   ` Vinicius Costa Gomes
2024-10-22  7:05     ` Lifshits, Vitaly [this message]
2024-10-22 18:50   ` Jacob Keller
2024-10-22 19:54     ` Joe Damato
2024-10-18 17:13 ` [Intel-wired-lan] [net-next v3 2/2] igc: Link queues " Joe Damato
2024-10-21 17:48   ` Vinicius Costa Gomes
2024-10-22  7:06     ` Lifshits, Vitaly
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=72483651-72ca-48b3-9726-b3acc1873bb8@intel.com \
    --to=vitaly.lifshits@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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