From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by dpdk.org (Postfix) with ESMTP id 0207B108A for ; Mon, 6 Mar 2017 10:17:44 +0100 (CET) Received: by mail-wm0-f45.google.com with SMTP id v186so58428470wmd.0 for ; Mon, 06 Mar 2017 01:17:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=C5e9CpIBvtwdOSG9g0Kc2qhpil2SSYnqZBUqoxNMq8M=; b=jlFoFZcprXwR4Q5Nh+kNmR1gI10gG/Zrqr10Zy/UGikX3eFaD4sEdVnn2KcpICK6Nf euSsYxRcrywGIIs0sT+jyibxlw1ABTCPybDec/Nuz+MxwzuySOxeei4kcQoVE8d3x5er OU9AW6Un0TeR9bs3GXoLjFwxyy1bbAo4AI94qg4OMhnofq+Y+sUhvp45JBn3BUjPJQLZ TdJu7FtsCaFN4LtYi2ErIK3eVLKZwOVtfcEHXgyLaSjAw42wGRFDR0GvPLMn49RASEsc fxaJLrypp1tlUwFDLKn9mxV4Z1mj/RVJzh1bT8iECu3x02nf+UBJoqm3dFSAO4fI2SNv SFRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=C5e9CpIBvtwdOSG9g0Kc2qhpil2SSYnqZBUqoxNMq8M=; b=PQZyEmoZN0sKcatqy151wHlNiMvepmX1ieW+MA7TATEAw4u5Ohm5c6jMRrFEkSuTHH V7DDQH4GkcP+HNxzWgnDQcp83wWZ7BP0f9n307CsMYDBfF7qYDFeRGw4ynv7g6skBQev CNBQv+05N5j+BgeS1i6G9RMkqvktzYO8A72A2slDmapmUznmKNWOugEVCyNweTD4+bKv zLj4futDQYHAknz7u2jcKLcRXxQcXzFOi0CcyVui0gLMjojJaHMmoaY0fGdoA+zPLgu3 mUfdG1UZgl5I5ibkYdIZ2iPa6FE20dR+43OFRRkFEhhHOnCUap7GodC5CFTKsYoiyxx5 FxHw== X-Gm-Message-State: AMke39khWP5FMaO/66FdNB9xFk8jOkbF9VB+qAY1IIAfanQxdWiXdMYAOEfdllKZRhDx1EP+ X-Received: by 10.28.191.24 with SMTP id p24mr12629424wmf.118.1488791864667; Mon, 06 Mar 2017 01:17:44 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id z70sm26196302wrc.2.2017.03.06.01.17.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 01:17:44 -0800 (PST) From: Thomas Monjalon To: Yuliang Li Cc: users@dpdk.org, "Wiles, Keith" Date: Mon, 06 Mar 2017 10:17:43 +0100 Message-ID: <2848144.mosHmk2WaE@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] difference between rte_eth_tx_buffer and rte_eth_tx_burst X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2017 09:17:45 -0000 2017-03-05 15:22, Wiles, Keith: > > > On Mar 4, 2017, at 7:46 PM, Yuliang Li wrote: > > > > Hi all, > > > > I am new to DPDK. I found 2 functions that can send packets: > > rte_eth_tx_buffer and rte_eth_tx_burst. I am confused about why we need > > these two different functions. To me, I can use only rte_eth_tx_burst, and > > rte_eth_tx_buffer does add more functional capability. Are there any other > > concerns like performance or others that we need these two functions? > > The best place to find out this type of information is to read the emails around the rte_eth_tx_buffer APIs in the archives. You may want to refine the search. > > https://mail-archive.com/search?a=1&l=dev%40dpdk.org&o=newest&haswords=rte_eth_tx_buffer The best place should be the documentation :) If someone is missing in the doc, please tell us what or make a patch. Thanks