From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.richardson@intel.com>
Received: from mga14.intel.com (mga14.intel.com [192.55.52.115])
 by dpdk.org (Postfix) with ESMTP id 153B712A8
 for <dev@dpdk.org>; Thu,  2 Jul 2015 11:20:44 +0200 (CEST)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by fmsmga103.fm.intel.com with ESMTP; 02 Jul 2015 02:20:43 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.15,391,1432623600"; d="scan'208";a="757112291"
Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.61])
 by orsmga002.jf.intel.com with SMTP; 02 Jul 2015 02:20:42 -0700
Received: by  (sSMTP sendmail emulation); Thu, 02 Jul 2015 10:20:41 +0025
Date: Thu, 2 Jul 2015 10:20:41 +0100
From: Bruce Richardson <bruce.richardson@intel.com>
To: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
Message-ID: <20150702092040.GA7688@bricha3-MOBL3>
References: <CABK1yFAeu3vJiGA8CVA+qd7OH6=sVQkx=BnisC81QTsy7P-Zsw@mail.gmail.com>
 <CABK1yFDWZmBABBaj8fWhGJA-J3V82Yp_=GwwgZHj+LSnFL_PDg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABK1yFDWZmBABBaj8fWhGJA-J3V82Yp_=GwwgZHj+LSnFL_PDg@mail.gmail.com>
Organization: Intel Shannon Ltd.
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Using rte_ring_mp_xyz() across EAL and non-EAL
 threads ?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2015 09:20:45 -0000

On Wed, Jul 01, 2015 at 10:50:49AM -0700, Gopakumar Choorakkot Edakkunni wrote:
> 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.

There are no core-specific elements for rte_rings, just for mempools. Yes, you
need a NUMA node ID when creating the ring, so that DPDK knows where to allocate
the memory for it. However, once that is done, the ring can safely be used from
both EAL and non-EAL threads. There is no requirement to have an lcore-id for
the thread.

/Bruce

> 
> On Wed, Jul 1, 2015 at 10:46 AM, Gopakumar Choorakkot Edakkunni
> <gopakumar.c.e@gmail.com> 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.