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 0DAB429D6 for ; Wed, 31 Jan 2018 15:46:13 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9412C20CF3; Wed, 31 Jan 2018 09:46:12 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 31 Jan 2018 09:46:12 -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=49d8xgjw9zT5LnSZtRkAm7jKv4 7MIdniIov9OHJ3nJ0=; b=Rcp/wjZxA3/d1z7lJg9C2nhyDsoB8rsjBhAH0oBahN TOnB1K6/pt/DOMWzprFLtucdzLi9pS6T4RZSSbKceoZMTbfcerxwQJSAHp/xPDbn Zv4JG7iD+7kYM2HrRT5MFQqd2QRaa3JwUe5Z5KdXvwmFTvoaBwl6xN1A6ftOeomp Q= 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=49d8xg jw9zT5LnSZtRkAm7jKv47MIdniIov9OHJ3nJ0=; b=pxCErEP/HUC2XNiTzy9Bbl Epwid9hmQYB0rT5MlXGuzNZpU3y+oQypspb/BVc4ZY/IpJT3setdEHuWZOqO6u8U RfqT1xZaAjhk2D54As4VU7rvxWsgvFspDlF0DeT0JvE2i1LC3UCAFJ4bHmlfKK67 i0BOjmC8g4QzzNZ2QTxxRLvG9rmshjGBzOGnDjDtQzbmJLflmvfL7uyPBBa9Hoqn 4/V5arg4tXugWLtvz5kwwz0lDV+yhl0ZxXL+7X/y/fyAeQxYS8UBEwNurwE6Ae9c 4JlDQdtCVI0XQcia5uR5x2xOEHhh2+bVsMaWJJTzd637Nxdn5qWI7oKuUjqFwHgA == 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 3CA8824608; Wed, 31 Jan 2018 09:46:12 -0500 (EST) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, hemant.agrawal@nxp.com, fiona.trahe@intel.com, rosen.xu@intel.com Date: Wed, 31 Jan 2018 15:45:26 +0100 Message-ID: <6226718.18SkXDHchy@xps> In-Reply-To: <20180131091318.7894-1-shreyansh.jain@nxp.com> References: <20180130145710.24757-1-shreyansh.jain@nxp.com> <20180131091318.7894-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 v4 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: Wed, 31 Jan 2018 14:46:13 -0000 31/01/2018 10:13, Shreyansh Jain: > The rawdevice implementation is targetted towards various accelerator use cases > which cannot be generalized within existing device models. Aim is to provided a > generalized structure at the cost of portability guarantee. Specific PMDs may > also expose any specific config APIs. Applications built over such devices are > special use-cases involving IP blocks. Applied with minor changes, doxygen fixes and compilation fixes.