DPDK-dev Archive on lore.kernel.org
 help / color / Atom feed
From: Harman Kalra <hkalra@marvell.com>
To: Soumen Chandra Laha <soumen.laha32@gmail.com>
Cc: users <users-bounces@dpdk.org>, <users@dpdk.org>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] L3fwd-power queue utilization issue
Date: Sat, 15 Feb 2020 14:21:01 +0530
Message-ID: <20200215085059.GA41850@outlook.office365.com> (raw)
In-Reply-To: <CAPJsYLHAWsvuyvm_RmMPeX69367rWX=Ed29yy7==0NE2LUfSQA@mail.gmail.com>

On Fri, Feb 14, 2020 at 05:35:53PM +0530, Soumen Chandra Laha 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.
>

We have tested l3fwd-power with octeontx2 PMD, l3fwd-power disables
queue interrupt even if a single packet is received on the queue.
I assume you are pumping multple flows to the nic.

> I am observing the below output:
> */root/comms/dpdk/examples/l3fwd-power/build/l3fwd-power  -l 2,3,4,5 -n 6
> --socket-mem 512,0  -w 17:00.0 -w 17:00.1  -- -p 0x3 --config
> '(0,0,2),(0,1,3),(1,0,4),(1,1,5)'  -P*
> EAL: Detected 48 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/l3fwd/mp_socket
> EAL: Probing VFIO support...
> EAL: PCI device 0000:17:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:158b net_i40e
> EAL: PCI device 0000:17:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:158b net_i40e
> Promiscuous mode selected
> POWER: Attempting to initialise ACPI cpufreq power management...
> POWER: Power management governor of lcore 2 has been set to user space
> successfully
> POWER: Initialized successfully for lcore 2 power management
> POWER: Power management governor of lcore 3 has been set to user space
> successfully
> POWER: Initialized successfully for lcore 3 power management
> POWER: Power management governor of lcore 4 has been set to user space
> successfully
> POWER: Initialized successfully for lcore 4 power management
> POWER: Power management governor of lcore 5 has been set to user space
> successfully
> POWER: Initialized successfully for lcore 5 power management
> Initializing port 0 ... Creating queues: nb_rxq=2 nb_txq=4... Port 0
> modified RSS hash function based on hardware support,requested:0x20820
> configured:0x820
>  Address:00:E0:ED:96:2B:AA, Allocated mbuf pool on socket 0
> Initializing rx queues on lcore 2 ... rxq=0,0,0
> Initializing rx queues on lcore 3 ... rxq=0,1,0
> Initializing rx queues on lcore 4 ... rxq=1,0,0
> Initializing rx queues on lcore 5 ... rxq=1,1,0
> 
> Checking link status.....done
> Port 0 Link Up - speed 25000 Mbps - full-duplex
> Port 1 Link Up - speed 25000 Mbps - full-duplex
> L3FWD_POWER: entering main loop on lcore 3
> L3FWD_POWER:  -- lcoreid=3 portid=0 rxqueueid=1
> L3FWD_POWER: entering main loop on lcore 4
> L3FWD_POWER:  -- lcoreid=4 portid=1 rxqueueid=0
> L3FWD_POWER: entering main loop on lcore 5
> L3FWD_POWER:  -- lcoreid=5 portid=1 rxqueueid=1
> EAL: Event already been added.
> L3FWD_POWER: entering main loop on lcore 2
> L3FWD_POWER:  -- lcoreid=2 portid=0 rxqueueid=0
> EAL: Event already been added.
> L3FWD_POWER: lcore 3 sleeps until interrupt triggers
> L3FWD_POWER: lcore 4 sleeps until interrupt triggers
> L3FWD_POWER: lcore 5 sleeps until interrupt triggers
> L3FWD_POWER: lcore 2 sleeps until interrupt triggers
> L3FWD_POWER: lcore 3 is waked up from rx interrupt on port 0 queue 1
> L3FWD_POWER: lcore 3 sleeps until interrupt triggers
> L3FWD_POWER: lcore 5 is waked up from rx interrupt on port 1 queue 1
> L3FWD_POWER: lcore 5 sleeps until interrupt triggers
> 
> I would appreciate it if some expert can shade a light on this.
> 
> Thanks & Regards,
> Soumen

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 12:05 Soumen Chandra Laha
2020-02-15  8:51 ` Harman Kalra [this message]

Reply instructions:

You may reply publically 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=20200215085059.GA41850@outlook.office365.com \
    --to=hkalra@marvell.com \
    --cc=dev@dpdk.org \
    --cc=soumen.laha32@gmail.com \
    --cc=users-bounces@dpdk.org \
    --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

DPDK-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \
		dev@dpdk.org
	public-inbox-index dpdk-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git