From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 7E6DB1B026 for ; Thu, 25 Jan 2018 23:22:36 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1BA0321CB7; Thu, 25 Jan 2018 17:22:36 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 25 Jan 2018 17:22:36 -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=bHdxt1yhdenB0V/kaDRMEYr+vP KBXC8aw2nO35t9rcE=; b=eocjBxrmVUwsS5ec8EMq1ilt7Dh5E1hTiEjLduXTxx L3mEYYMnjj90ZB9r7jd08Ydcctkh84uY/YG1Vb4iDoX1vzGkCGnVw2X5dY+P/y2o cxbP9SF91X/Mhh5D52Ww2cRV5albjCY/P7PRmj+U78eQz4JS6kg2x9FxPj2fW8RT c= 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=bHdxt1 yhdenB0V/kaDRMEYr+vPKBXC8aw2nO35t9rcE=; b=kRg4JcVO/tukVf3dCvlzLU A1a5r5ORZdwkmeIJIK4pjZqwiXH0a9QbVK01E04gAcOBHzaC3oNcSBPmLCJ/IWsi I6TsNYO5NBdEDF49OC27woJ5VhxDKAZjDb/YCy0/5dN2xZYQemzJ5DUOelymMMsY wlsWhnRk7ZU4QzVrVY9H8WTVdjEq8DRvy4Ifm+MIhf7vj2joFYaUz5JtmQppU+7k CYnaxmfz1N1d+l3q6qMdbz64ZQIoMGNGeVanPkF/44RkORf2VuvHwZfn0dZKfrT3 mIHemfW7C1v1yWn0EG8RYjkiwrPvzDMBe+W5IOL7R+D9tQX2soxf1VhXDVX5RN8g == 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 B395B24636; Thu, 25 Jan 2018 17:22:35 -0500 (EST) From: Thomas Monjalon To: dev@dpdk.org Cc: Shreyansh Jain , 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 Date: Thu, 25 Jan 2018 23:21:52 +0100 Message-ID: <3936585.LC0zCDCLAv@xps> In-Reply-To: <20180123135910.10755-1-shreyansh.jain@nxp.com> References: <20180102125749.2379-1-shreyansh.jain@nxp.com> <20180123135910.10755-1-shreyansh.jain@nxp.com> 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: Thu, 25 Jan 2018 22:22:36 -0000 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 :)