From: Stephen Hemminger <stephen@networkplumber.org>
To: Jack Humphries <jack@chillysky.com>
Cc: users@dpdk.org
Subject: Re: Enable RX interrupts
Date: Mon, 1 Nov 2021 12:51:36 -0700 [thread overview]
Message-ID: <20211101125136.55432b26@hermes.local> (raw)
In-Reply-To: <A04D1F16-6D1D-499A-A05F-64BD30D72726@chillysky.com>
On Mon, 1 Nov 2021 12:16:14 -0700
Jack Humphries <jack@chillysky.com> wrote:
> Thanks Stephen. I am just using one RX queue from the NIC. I assume that since I don’t need per-queue interrupts here since there is only one queue, I should be good using ixgbe+igb_uio?
>
> Thanks,
> Jack
>
Even with one queue, it won't work because the interrupt is dedicated to link status.
prev parent reply other threads:[~2021-11-01 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 5:50 Jack Humphries
2021-11-01 7:46 ` Dmitry Kozlyuk
2021-11-01 8:56 ` Jack Humphries
2021-11-06 15:12 ` Thomas Monjalon
2021-11-01 15:20 ` Stephen Hemminger
2021-11-01 19:16 ` Jack Humphries
2021-11-01 19:51 ` Stephen Hemminger [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=20211101125136.55432b26@hermes.local \
--to=stephen@networkplumber.org \
--cc=jack@chillysky.com \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).