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 33091A00C3 for ; Sun, 3 Jul 2022 22:19:01 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BA41940A80; Sun, 3 Jul 2022 22:19:00 +0200 (CEST) Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [152.66.248.44]) by mails.dpdk.org (Postfix) with ESMTP id 4EF6D4021F for ; Sun, 3 Jul 2022 22:18:59 +0200 (CEST) Received: from [192.168.1.145] (host-79-121-40-125.kabelnet.hu [79.121.40.125]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id 263KIrZn010386 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 3 Jul 2022 22:18:58 +0200 (CEST) (envelope-from lencse@hit.bme.hu) X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-40-125.kabelnet.hu [79.121.40.125] claimed to be [192.168.1.145] Message-ID: <2ca6fffa-05df-9882-34e9-6c13dc2cc28f@hit.bme.hu> Date: Sun, 3 Jul 2022 22:18:46 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: rte_eth_tx_burst() always returns 0 in tight loop Content-Language: en-US To: users@dpdk.org References: From: =?UTF-8?Q?G=c3=a1bor_LENCSE?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.103.2 at frogstar.hit.bme.hu X-Virus-Status: Clean Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.40.125; helo=[192.168.1.145]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; X-DCC--Metrics: frogstar.hit.bme.hu; whitelist X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, AWL, SARE_ADLTSUB2 autolearn=disabled version=3.4.1-frogstar X-Spam-Checker-Version: SpamAssassin 3.4.1-frogstar (2015-04-28) on frogstar.hit.bme.hu X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Dear Antonio, According to my experience, the rte_eth_tx_burst() function reports the packets as "sent" (by a non-zero return value), when they are still in the transmit buffer. (If you are interested in the details, you can see them in Section 3.6.5 of this paper: http://www.hit.bme.hu/~lencse/publications/e104-b_2_128.pdf ) Therefore, I think that the return value of 0 may mean that rte_eth_tx_burst() can't even commit itself for the future delivery of the packets. I could only guess why. E.g. all its resources have been exhausted. Best regards, Gábor 7/3/2022 5:57 PM keltezéssel, Antonio Di Bacco írta: > I'm trying to send packets continuously in a tight loop with a burst > size of 8 and packets are 9600 bytes long. > If I don't insert a delay after the rte_eth_tx_burst it always returns 0. > > What's the explanation of this behaviour ? > > Best regards, > Antonio.