All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
Cc: dev@dpdk.org
Subject: Re: Multiple Tx-Queues not working as expected
Date: Thu, 16 Feb 2023 11:51:09 -0800	[thread overview]
Message-ID: <20230216115109.07067372@hermes.local> (raw)
In-Reply-To: <CAGA5_H7TO_ioqKkCpsZy=674yET=6O5K-AW9Jw0vijqB5HH24w@mail.gmail.com>

On Thu, 16 Feb 2023 23:40:27 +0530
Rajasekhar Pulluru <pullururajasekhar@gmail.com> wrote:

> Hi Team,
> 
> I am trying to set-up 8 Tx-Queues (but only 1 Rx-Queue) and burst traffic
> out of different Tx-Queues from the same cpu core on an ixgbe nic (10G).
> Although transmitted packets reach the peer, reading the statistics
> indicates only the Tx-q[0] has non-zero packets and bytes count, the rest
> of the Tx-q[1] to Tx-q[7] all have zero packets and bytes count.
> 
> I am following the below sequence.
> 
> 1. configuration
> rte_eth_dev_configure(port-id, 1 /* only 1 rx-q */, 8 /* tx-queues */,
> &dev_conf /* memset of 0 on this dev_conf done */);
> 
> 2. tx queue set-up
> struct rte_eth_dev_info dev_info;
> rte_eth_dev_info_get(port-id, &dev_info);
> 
> struct rte_eth_txconf tx_conf;
> memcpy(&tx_conf, &dev_info.default_txconf, sizeof tx_conf);
> for(i=0; i<8; i++) {
> rte_eth_tx_queue_setup(port-id, i /* queue-id */, 1024 /* num_of_txdesc */,
> numa_node, &tx_conf;)
> }
> 
> 3. rx queue set-up
> rte_eth_rx_queue_setup(port-id, 0, 1024 /* num_of_rxdesc */, &rx_conf,
> mbuf_pool);
> 
> 4. start the port
> rte_eth_dev_start(port-id);
> 
> 5. call the below tx burst function with different queue-id (range 0 to 7)
> every-time for every burst of new packets to be transmitted
> rte_eth_tx_burst(port-id, queue-id, pkts_burst, nb_pkts_burst);
> 
> 6. read stats using rte_eth_xstats_get and verified that only the first
> tx-q has non-zero packets and bytes count, rest of the tx-q's have 0
> packets and bytes count.
> 
> What could be wrong here? Appreciate any help.
> 
> Thanks & Regards,
> Rajasekhar
> ReplyForward

Depending on the type of NIC, some share a signal completion channel
for both RX and TX. If the Rx channel is not polled, than transmit completions
may not happen.

  reply	other threads:[~2023-02-16 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 18:10 Multiple Tx-Queues not working as expected Rajasekhar Pulluru
2023-02-16 19:51 ` Stephen Hemminger [this message]
2023-02-17  6:00   ` Rajasekhar Pulluru
2023-02-17 16:26     ` Stephen Hemminger
2023-02-17 17:33       ` Rajasekhar Pulluru
2023-02-17 16:38     ` Bruce Richardson
2023-02-17 17:38       ` Rajasekhar Pulluru

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=20230216115109.07067372@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=pullururajasekhar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.