From: Stephen Hemminger <stephen@networkplumber.org>
To: Soumen Chandra Laha <soumen.laha32@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] L3fwd-power queue utilization issue.
Date: Sun, 16 Feb 2020 14:45:25 -0800 [thread overview]
Message-ID: <20200216144525.1886c176@hermes.lan> (raw)
In-Reply-To: <CAPJsYLG2Mr7FMe5oOSSFXD3docNdODjUPT_PXyPqNSM5WwgF0w@mail.gmail.com>
On Fri, 14 Feb 2020 16:36:04 +0530
Soumen Chandra Laha <soumen.laha32@gmail.com> wrote:
> Hi,
>
> I'm trying to run l3fwd-power application for 2 Port with queue. Always
> only queue 1 of port 0 and port 1 are utilized.
> CPU C-state, hpet are enabled, ports are binded to igb_uio.
> Tried with NIC's x772 (10 GbE) and XXV710(25 GbE), Observed same behavior.
>
Igb_uio does not support per-queue interrupts. That needs MSI-X which is
only supported by VFIO-pci.
next prev parent reply other threads:[~2020-02-16 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 11:06 Soumen Chandra Laha
2020-02-16 22:45 ` Stephen Hemminger [this message]
2020-02-17 5:57 ` Soumen Chandra Laha
2020-02-14 12:05 Soumen Chandra Laha
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=20200216144525.1886c176@hermes.lan \
--to=stephen@networkplumber.org \
--cc=soumen.laha32@gmail.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).