From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 65300A0096 for ; Tue, 4 Jun 2019 14:23:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2C44D1BA7F; Tue, 4 Jun 2019 14:23:08 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 957241B9C3 for ; Tue, 4 Jun 2019 14:23:06 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2019 05:23:04 -0700 X-ExtLoop1: 1 Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.51]) by fmsmga001.fm.intel.com with SMTP; 04 Jun 2019 05:23:03 -0700 Received: by (sSMTP sendmail emulation); Tue, 04 Jun 2019 13:23:02 +0100 Date: Tue, 4 Jun 2019 13:23:02 +0100 From: Bruce Richardson To: Thomas Monjalon Cc: dev@dpdk.org Message-ID: <20190604122301.GA1322@bricha3-MOBL.ger.corp.intel.com> References: <20190530212525.40370-1-bruce.richardson@intel.com> <20190530212525.40370-9-bruce.richardson@intel.com> <2132695.1Z5KPACmLg@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2132695.1Z5KPACmLg@xps> User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-dev] [PATCH 8/8] raw/ioat: add local API to perform copies 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Jun 03, 2019 at 04:44:17PM +0200, Thomas Monjalon wrote: > 30/05/2019 23:25, Bruce Richardson: > > Add local APIs to trigger data copies, and retrieve handle values once > > those copies are completed. Included are unit tests to validate the data > > is copies correctly. > > Would be nice to have a small design overview in the guide. > > We may need also to answer these questions: > What are the performance gains? In which use-case? > What are the hardware requirements? > Thanks for the comments. Will try and add more details in subsequent revisions. /Bruce