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 D0918A0C47 for ; Wed, 14 Jul 2021 18:32:18 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 996804068A; Wed, 14 Jul 2021 18:32:18 +0200 (CEST) Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [152.66.248.44]) by mails.dpdk.org (Postfix) with ESMTP id 6999D4014D for ; Wed, 14 Jul 2021 18:32:17 +0200 (CEST) Received: from [192.168.1.146] (host-79-121-43-67.kabelnet.hu [79.121.43.67]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id 16EGWB6A071626 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 14 Jul 2021 18:32:16 +0200 (CEST) (envelope-from lencse@hit.bme.hu) X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-43-67.kabelnet.hu [79.121.43.67] claimed to be [192.168.1.146] To: users@dpdk.org References: <20210714081530.07d2cbbd@hermes.local> From: =?UTF-8?Q?G=c3=a1bor_LENCSE?= Message-ID: <4b5c74ba-bca4-a0eb-680f-761207162a1f@hit.bme.hu> Date: Wed, 14 Jul 2021 18:32:07 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210714081530.07d2cbbd@hermes.local> Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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.43.67; helo=[192.168.1.146]; 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=-1.0 required=5.0 tests=ALL_TRUSTED,AWL,TW_PD 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 Subject: Re: [dpdk-users] Dpdk multi core packet acquisition. 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 Sender: "users" I recommend you to use multi queue receiving (RSS). Thus you do not need to use mutual exclusion. (Performance!) Of course, you need some entropy for the hash function to distribute the packets approximately evenly among the queues. Gábor 2021.07.14. 17:15 keltezéssel, Stephen Hemminger írta: > On Wed, 14 Jul 2021 10:32:56 +0200 > Nirmal R wrote: > >> Hello All, >> >> I need to acquire packets from a source at more than 40Gbps. I was thinking >> to use rx_burst in a function with more than one core and load it into a >> ring. My question is, will the packets received will be in order between >> the cores say core 1 receives packet 1,2,3 and core 2 receives packet 4,5,6 >> or will it be in out of order(Random). Also can we combine 2 cores to >> launch one function. >> >> Thank you, >> >> With Regards, >> Nirmalraj R > DPDK drivers assume a single core at a time is reading a single queue. > If you have multiple cores reading a single queue then you need to do > some form of mutual exclusion in your application. > > This is in the documentation