From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0116.outbound.protection.outlook.com [157.56.110.116]) by dpdk.org (Postfix) with ESMTP id EF5487E74 for ; Thu, 25 Sep 2014 21:21:09 +0200 (CEST) Received: from BL2PR05MB115.namprd05.prod.outlook.com (10.255.232.25) by BL2PR05MB051.namprd05.prod.outlook.com (10.255.228.151) with Microsoft SMTP Server (TLS) id 15.0.1039.15; Thu, 25 Sep 2014 19:27:23 +0000 Received: from BL2PR05MB113.namprd05.prod.outlook.com (10.255.232.20) by BL2PR05MB115.namprd05.prod.outlook.com (10.255.232.25) with Microsoft SMTP Server (TLS) id 15.0.1039.15; Thu, 25 Sep 2014 19:27:21 +0000 Received: from BL2PR05MB113.namprd05.prod.outlook.com ([169.254.1.168]) by BL2PR05MB113.namprd05.prod.outlook.com ([169.254.1.168]) with mapi id 15.00.1039.011; Thu, 25 Sep 2014 19:27:22 +0000 From: Anjali Kulkarni To: Matthew Hall , Jeff Shaw Thread-Topic: [dpdk-dev] DPDK Demos at IDF conference using DDIO Thread-Index: AQHP2NQbybjvXDH8v0u8fl+daafsnpwSBQwAgAA0OgD//40vgA== Date: Thu, 25 Sep 2014 19:27:21 +0000 Message-ID: References: <20140925161124.GA7609@plxv1142.pdx.intel.com> <20140925191820.GA3117@mhcomputing.net> In-Reply-To: <20140925191820.GA3117@mhcomputing.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [66.129.239.10] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2PR05MB115;UriScan:; x-forefront-prvs: 0345CFD558 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(30513003)(189002)(377454003)(164054003)(479174003)(51704005)(199003)(46102003)(79102003)(81342003)(74662003)(4396001)(107046002)(81542003)(77982003)(20776003)(64706001)(66066001)(74502003)(21056001)(80022003)(2656002)(85852003)(85306004)(83072002)(105586002)(83506001)(95666004)(83322001)(19580395003)(101416001)(87936001)(106116001)(85806002)(106356001)(76176999)(77096002)(76482002)(86362001)(97736003)(120916001)(54356999)(36756003)(31966008)(90102001)(92726001)(19580405001)(50986999)(99396003)(92566001)(10300001)(99286002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR05MB115; H:BL2PR05MB113.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2PR05MB051; X-OriginatorOrg: juniper.net Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] DPDK Demos at IDF conference using DDIO X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 19:21:10 -0000 Actually, in the demo that I saw they had probably used as many of the accelerations as possible to get the kind of rates they described. Even if we could see (a documentation of) what all things they used in this particular application, it would help. >>From my discussions, it seemed as if there were some specific lookup APIs that they used to get better performance. Anjali On 9/25/14 12:18 PM, "Matthew Hall" wrote: >On Thu, Sep 25, 2014 at 09:11:24AM -0700, Jeff Shaw wrote: >> Intel(R) Data Direct I/O Technology (Intel(R) DDIO) is a feature >>introduced=20 >> with the Intel(R) Xeon(R) processor E5 family. >>=20 >> It has been around for several years and is available at least on all >>Xeon=20 >> E5 processors. DDIO is part of the platform, so any DPDK version can >>take=20 >> advantage of the feature. There are several papers and videos >>available on=20 >> the Internet that can provide more details. > >One difficulty I run into with a lot of these Intel accelerations... each >one=20 >is described as an atomic entity independent of all the other possible >accelerations. Nobody explains how to take all of them together to make a >complete high-speend low-latency packet processing solution from L1-L7. > >It'd be nice to see an architecture level view of DPDK, along with the >accelerations one could / should apply at each level, so there's some >kind of=20 >checklist you can follow to be sure you used everything you should where >you=20 >should. Otherwise you'll miss some stuff and waste the features you paid >for. > >Also, how is DDIO different from the previous DCA accelerations? > >Thanks, >Matthew.