From: Srivats P <pstavirs@gmail.com>
To: Zvi Effron <zeffron@riotgames.com>
Cc: Xdp <xdp-newbies@vger.kernel.org>
Subject: Re: IRQ assignment for queues
Date: Thu, 22 Apr 2021 21:01:03 +0530 [thread overview]
Message-ID: <CANzUK5_i9cynLiTB8-C-S90_7K_YutTcn8nDvxboKWU0=wfe4A@mail.gmail.com> (raw)
In-Reply-To: <CAC1LvL3rFo8YaMyRim=MpYP00a9ZH2c8X=J-hxiM48=SBm+Xuw@mail.gmail.com>
On Thu, Apr 22, 2021 at 3:14 AM Zvi Effron <zeffron@riotgames.com> wrote:
>
> On Tue, Apr 20, 2021 at 11:57 PM Srivats P <pstavirs@gmail.com> wrote:
> >
> > Hi,
> >
> > Not a XDP question, but more generic about IRQ assignment for queues.
> >
> > For a NIC which has separate RX and TX queues (no COMBINED queues), I
> > see in /proc/interrupts that only 1 IRQ is assigned.
> >
> > ...
> >
> > srivatsp@EXA8:~$ cat /proc/interrupts | grep enp5s0f1
> > 73: 0 2 0 0 ITS-MSI 2623488
> > Edge enp5s0f1-rxtx-0
> > 89: 0 0 0 0 ITS-MSI 2623504
> > Edge enp5s0f1-rbdr-0
> > 92: 0 0 0 0 ITS-MSI 2623507
> > Edge enp5s0f1-qset-err-0
> >
> > Is the IRQ for the RX queue or TX queue or both? Does Tx need an IRQ?
>
> I see the IRQ name has "rxtx" in it. From my experience, that's the
> same type of designation used for combined queues, and indicates that
> the IRQ is for both RX and TX.
I guessed as much (based on i40e combined TxRx queues experience), but
wanted to confirm.
> I'm not sure which driver you're using,
This output and query was for the Cavium ThunderX nic_vf driver specifically.
> though, and my experience is mostly with i40e and ena drivers, so it
> could be incorrect when applied to your case.
>
> --Zvi
prev parent reply other threads:[~2021-04-22 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 6:57 IRQ assignment for queues Srivats P
2021-04-21 21:44 ` Zvi Effron
2021-04-22 15:31 ` Srivats P [this message]
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='CANzUK5_i9cynLiTB8-C-S90_7K_YutTcn8nDvxboKWU0=wfe4A@mail.gmail.com' \
--to=pstavirs@gmail.com \
--cc=xdp-newbies@vger.kernel.org \
--cc=zeffron@riotgames.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 read-only IMAP folder(s) and NNTP newsgroup(s).