From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by dpdk.org (Postfix) with ESMTP id AEF95231C for ; Mon, 19 May 2014 12:59:30 +0200 (CEST) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 19 May 2014 03:59:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,866,1392192000"; d="scan'208";a="433902745" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by azsmga001.ch.intel.com with ESMTP; 19 May 2014 03:59:37 -0700 Received: from irsmsx153.ger.corp.intel.com (163.33.192.75) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 19 May 2014 11:59:19 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.183]) by IRSMSX153.ger.corp.intel.com ([169.254.9.50]) with mapi id 14.03.0123.003; Mon, 19 May 2014 11:59:18 +0100 From: "Richardson, Bruce" To: Neil Horman Thread-Topic: [dpdk-dev] [PATCH 0/3] ring: provide rte_ring_as_ethdev API Thread-Index: AQHPcTLQj29A2eJnDkiAhShxbpRNCJtDfVCAgARBarA= Date: Mon, 19 May 2014 10:59:18 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B01AA1B2C5@IRSMSX103.ger.corp.intel.com> References: <1400264114-28455-1-git-send-email-bruce.richardson@intel.com> <20140516185417.GC5432@hmsreliant.think-freely.org> In-Reply-To: <20140516185417.GC5432@hmsreliant.think-freely.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH 0/3] ring: provide rte_ring_as_ethdev API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 10:59:31 -0000 > -----Original Message----- > From: Neil Horman [mailto:nhorman@tuxdriver.com] > Sent: Friday, May 16, 2014 7:54 PM > To: Richardson, Bruce > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 0/3] ring: provide rte_ring_as_ethdev API >=20 > On Fri, May 16, 2014 at 07:15:11PM +0100, Bruce Richardson wrote: > > > NAK, I don't think this makes sense. If you want to encapsulate a ring p= air as > an ethdev, then write a pmd that does so. That will give you a standardi= zed > ethdev that you can create using the existing --vdev librte_eal command l= ine > options without having to widen your API surface, or having to write > applications that specifically know about the fact that your ethdev is co= mposed > of rings under the covers. >=20 The objective is not to "encapsulate a ring pair", but instead allow a ring= to be "type-cast" to an ethdev for the purposes of rx and tx.=20 If this is provided, we can provide standard functions which work to take p= ackets in using rx_burst and which send packets out after processing using = tx_burst. The same code can then be used unmodified without worrying about = whether the packets come from/to a NIC or from another core (via ring).