From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 6E6871B33E for ; Tue, 30 Jan 2018 00:49:52 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0B1D720C6D; Mon, 29 Jan 2018 18:49:52 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 29 Jan 2018 18:49:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=JxzjaiAWzQ0Z6lIbV+Ttix9ug7 7MZ+hPOEW0XOQKffM=; b=jpN1Aj+OBnEOGW/XB4EMPS6nldfDJqeXwVzibwco/4 Gt5v1iyRf37cBc+gUoZterywO1KRi8elf+1zYchIndPlQj01JUyk0WchBrDVKC8r gs161bI3hmtK+Hv8hu7LUNioOKH2cUoYD2dQng6fqAhISBX91oEML23aq//VEUWJ M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Jxzjai AWzQ0Z6lIbV+Ttix9ug77MZ+hPOEW0XOQKffM=; b=St+GA/uCmavol9BsTFoOvt bJNa6zrUkU7LWdfGEYjQx4y+oCb1FBvmgXmUAuNlfebQIdYKLwzf3D/sUd1Xuepp XbFvRoBbqI5NYEgHeCOWZRFxWdLitQUYEK3L+kT3LhW+Uk9qWk08wE/NBISVPAv9 iPdo2n29zUVoHlXV8cRPcGSB4Ol8fr7p2u1nsElnZfSNzr0z/6N59/MAmk6QK6u5 d5Cz4IdbTgG0nQT497k5PSUD5AyCOtqQOylR+SW/W6+xAJW+WIBTWzR46Mm1rtmO LbE9hQagTSbJ0Qsn0qA8nWOEu4n8198jVSO4cbLp3VTHX7wNwPDO4PkVlD9D5yzw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id C2277241E0; Mon, 29 Jan 2018 18:49:51 -0500 (EST) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, fiona.trahe@intel.com, hemant.agrawal@nxp.com, rosen.xu@intel.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, olivier.matz@6wind.com, jerin.jacob@caviumnetworks.com, Neil Horman , ferruh.yigit@intel.com Date: Tue, 30 Jan 2018 00:49:05 +0100 Message-ID: <1697434.V3Jmbt3P0N@xps> In-Reply-To: <3936585.LC0zCDCLAv@xps> References: <20180102125749.2379-1-shreyansh.jain@nxp.com> <20180123135910.10755-1-shreyansh.jain@nxp.com> <3936585.LC0zCDCLAv@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 00/10] Introduce generic 'rawdevice' support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 23:49:52 -0000 25/01/2018 23:21, Thomas Monjalon: > 23/01/2018 14:59, Shreyansh Jain: > > Defining a very generic super-set of device type and its device operations that > > can be exposed such that any new/upcoming/experimental device can be layered > > over it. 'rawdevice' semantic in this patchset represents a device that doesn't > > have any flavor/type associated with it which is advertised (like net, crypto > > etc). > > > > A *rte_rawdevice* is a raw/generic device without any standard configuration > > or input/output method assumption. > > Please HELP! > Some reviews would be more than welcome :) No review at all of this new driver class? Shreyansh, please could you rebase on latest master and add the __rte_experimental tag as done in this commit: http://dpdk.org/commit/77b7b81e32e Thanks