From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gopakumar Choorakkot Edakkunni Subject: Re: Using rte_ring_mp_xyz() across EAL and non-EAL threads ? Date: Wed, 1 Jul 2015 10:50:49 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 To: dev@dpdk.org Return-path: Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by dpdk.org (Postfix) with ESMTP id 862E6A10 for ; Wed, 1 Jul 2015 19:50:50 +0200 (CEST) Received: by ieqy10 with SMTP id y10so40140332ieq.0 for ; Wed, 01 Jul 2015 10:50:50 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" rte_ring_create() needs a socket-id though and seems to be allocating core-specific memory pools for the ring ? But my non-EAL app thread is not bound to any core, so now I am wondering if that will work. Rgds, Gopa. On Wed, Jul 1, 2015 at 10:46 AM, Gopakumar Choorakkot Edakkunni wrote: > Hi, > > I have a requirement where one of my non-EAL app threads needs to > handoff some packets to an EAL task. I was thinking of using > rte_ring_mp_enqueue/dequeue for that purpose. I looked at the code for > the rte_ring library and it doesnt look like it has any "EAL" > dependencies, but I wanted to double confirm that there are no issues > in using it that way. Dint find much yes/no info about that on the > mailers/docs. Pls let me know your thoughts. > > Rgds, > Gopa.