From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4A24141CB5; Thu, 16 Feb 2023 20:51:13 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2394842D12; Thu, 16 Feb 2023 20:51:13 +0100 (CET) Received: from mail-pl1-f169.google.com (mail-pl1-f169.google.com [209.85.214.169]) by mails.dpdk.org (Postfix) with ESMTP id 9658740E25 for ; Thu, 16 Feb 2023 20:51:11 +0100 (CET) Received: by mail-pl1-f169.google.com with SMTP id be8so3215624plb.7 for ; Thu, 16 Feb 2023 11:51:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=ZgcvlN6aC2y+fJFY5nhjMI3cUajP3BLSZaKwOKoTGBc=; b=Jg77ZPOVo3oatH4/jbCi7YUQ+3Z48duDOMnCWm6R3VJqWQb2sjEvM3QzCoEWdWcn/O PYdx607h/2IOWo4ro71WDhD7uL7zWr919fztXP9qEDLFQjjuF4ckUsr1c6SerHtAQk8N NdKw0CV1Kekj6LQ2PNWbrkyek5JDHtlIMEuLPOfh2Ia/RRiD7KXs1/3WGssJRK+Q7/XW jL7mq9nd71eYayK7093pvKouqnBgwFRjbtEiD/TqVkip3oTZYGBNJwonitNPYQDIfu/w 9sWbJXr015j+uUtRZdbgbprapuyI8PYWe+TEBfXtaJ+v2AOt5a0CzxAefnxQJG2dysSI kWUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZgcvlN6aC2y+fJFY5nhjMI3cUajP3BLSZaKwOKoTGBc=; b=gPx31mYzNCwXMuxrHDNeDJNX6/BQxO9/y9Ol2c87W6L9ukYjnb+mvgnwDjRqE8VBWq h4isbMn8GrmJ0RK9uNJHyj4PAmSGt2ZEVmZMHFFzywwxbGFtwGStdaHRN9x4SppB6GqJ 2tVmLdE8ifJLCEdGf9AnhIuD9z6r+kfwhfNMFAluQkTOw/VZasCfZHst5iexWc1Lj1w6 C45do92t8QnY+aeouSuftMZpGNPoB57yIp0SxSwYhzbRkcnzqLSEek2amJIs8DUgyBlY DDn4sEU3BZPHLSOHt0Qnye8YcYdbZXK7gL+OlLgzxdy6ITfD+eE8COI5o0e3zxI0A3G/ aTSw== X-Gm-Message-State: AO0yUKXn2x2XhL9xc/9UhxSJz9XogCPUNm9WGUi52126KqUs6XAu1fZS zpEkUPVrNPXVHMcN4BgfeX12vA== X-Google-Smtp-Source: AK7set9FZGRfKHAYKAeEbB52KyH0OcyPg4XliMhhxPGjIjSpAMPOD6CJv/hnG271fe1ypoy4iEoYJg== X-Received: by 2002:a17:90b:1b0b:b0:234:e3f:f52d with SMTP id nu11-20020a17090b1b0b00b002340e3ff52dmr8495451pjb.2.1676577070716; Thu, 16 Feb 2023 11:51:10 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id b9-20020a63d809000000b004fb71d96d78sm1546588pgh.2.2023.02.16.11.51.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Feb 2023 11:51:10 -0800 (PST) Date: Thu, 16 Feb 2023 11:51:09 -0800 From: Stephen Hemminger To: Rajasekhar Pulluru Cc: dev@dpdk.org Subject: Re: Multiple Tx-Queues not working as expected Message-ID: <20230216115109.07067372@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Thu, 16 Feb 2023 23:40:27 +0530 Rajasekhar Pulluru 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.