From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C6093A046B for <public@inbox.dpdk.org>; Thu, 27 Jun 2019 17:34:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 09DF02BF7; Thu, 27 Jun 2019 17:34:31 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 116C12BF4 for <dev@dpdk.org>; Thu, 27 Jun 2019 17:34:29 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jun 2019 08:34:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,424,1557212400"; d="scan'208";a="173169429" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga002.jf.intel.com with ESMTP; 27 Jun 2019 08:34:27 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.159]) by IRSMSX153.ger.corp.intel.com ([169.254.9.60]) with mapi id 14.03.0439.000; Thu, 27 Jun 2019 16:34:26 +0100 From: "Van Haaren, Harry" <harry.van.haaren@intel.com> To: "Richardson, Bruce" <bruce.richardson@intel.com>, "dev@dpdk.org" <dev@dpdk.org> CC: "thomas@monjalon.net" <thomas@monjalon.net>, "jerinj@marvell.com" <jerinj@marvell.com>, "Richardson, Bruce" <bruce.richardson@intel.com>, "Burakov, Anatoly" <anatoly.burakov@intel.com> Thread-Topic: [dpdk-dev] [PATCH v3 0/8] raw/ioat: driver for Intel QuickData Technology Thread-Index: AQHVLNTjQpq+3akJf0K6mJGQFtQe+KavoBAg Date: Thu, 27 Jun 2019 15:34:26 +0000 Message-ID: <E923DB57A917B54B9182A2E928D00FA675886C66@IRSMSX102.ger.corp.intel.com> References: <20190530212525.40370-1-bruce.richardson@intel.com> <20190627104055.8244-1-bruce.richardson@intel.com> In-Reply-To: <20190627104055.8244-1-bruce.richardson@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiN2E5OWM1MjYtN2M3Yy00OTJkLThkNjktNzE4NTdmYzA2YTgwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZDFDanRjSGNUWHZwUVZQSjU0c0RFcGhRRVR6UTV1ZWJJWEJxdnFERGF0a3BTNjhvbUNLMzFmQmx6Ylh0SEd5VSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3 0/8] raw/ioat: driver for Intel QuickData Technology X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson > Sent: Thursday, June 27, 2019 11:41 AM > To: dev@dpdk.org > Cc: thomas@monjalon.net; jerinj@marvell.com; Richardson, Bruce > <bruce.richardson@intel.com> > Subject: [dpdk-dev] [PATCH v3 0/8] raw/ioat: driver for Intel QuickData > Technology >=20 > This patch series adds support for the Intel QuickData Technology > device, part of the Intel I/O Acceleration Technology (Intel I/OAT). It > is a raw device for allowing hardware DMA i.e. data copies in hardware. >=20 > Performing the copies in hardware can provide performance improvements > for applications where the average copy size is reasonably large, e.g. > 1k packets. For smaller packets, e.g. 64-256 bytes, offloading the copy > may reduce performance due to the overhead of using hardware. Applied (release notes conflict - but that's par for the course close to in= tegration) Build each patch with meson (git rebase -x is awesome :) Ran unit tests: $ ioat_rawdev_probe(): Init 0000:00:04.0 on NUMA node 0 $ failed_enqueues: 0 successful_enqueues: 3300 copies_started: 3300 c= opies_completed: 3300 All seems fine to me; Series-Tested-by: Harry van Haaren <harry.van.haaren@intel.com>