From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0.salzburgresearch.at (mx0.salzburgresearch.at [78.104.175.164]) by dpdk.org (Postfix) with ESMTP id 539918D35 for ; Wed, 2 Sep 2015 09:23:45 +0200 (CEST) X-Virus-Scanned: by Salzburg Research on mx0.salzburgresearch.at DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=salzburgresearch.at; s=srfg; t=1441178624; bh=7VgBScaomw2SWPGSlYDcL00HatxigCd85OaWhiU6z88=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=P3nePYTyt3vz95cOdnHMxhqMy/BQaFxBVtf5QpYrQfhnFzVW7c3pM8ISw7QaZEBEj Kv0EDZV12UoldlNocSSk+3PnRzEwnAnKNt6rwhRqfQbM659uZK79wzkzjLefxFti/4 WyRp+sCy1kwq54/AKX5UjkcIQFbsTjDUrf7Xs+3s= Received: from mail01.salzburgresearch.at (mail01.salzburgresearch.at [172.16.0.31]) by mx0.salzburgresearch.at (Postfix) with ESMTPS id D6E7A200EC2; Wed, 2 Sep 2015 09:23:42 +0200 (CEST) Received: from [172.16.96.142] (anc42.salzburgresearch.at [172.16.96.142]) by mail01.salzburgresearch.at (Postfix) with ESMTPSA id A33233C8C; Wed, 2 Sep 2015 09:23:42 +0200 (CEST) To: Declan Doherty , "dev@dpdk.org" References: <55E5A7A5.3080202@salzburgresearch.at> <55E5A80F.70508@salzburgresearch.at> <55E5A8A5.7000502@salzburgresearch.at> <55E5CC53.90708@intel.com> From: Stefan Binna Message-ID: <55E6A3FE.9090408@salzburgresearch.at> Date: Wed, 2 Sep 2015 09:23:42 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55E5CC53.90708@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Thomas Pfeiffenberger , =?UTF-8?Q?Ferdinand_T=c3=bcllenburg?= Subject: Re: [dpdk-dev] Fast Failover Test Results 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: Wed, 02 Sep 2015 07:23:45 -0000 Am 01.09.2015 um 18:03 schrieb Declan Doherty: > > > On 01/09/15 14:31, Stefan Binna wrote: >> Hi @all, >> >> I've conducted some fast failover tests on a SDN infrastructure, whereby >> following three configurations were used for the device under test >> (DUT): >> >> - Intel 82574L with default driver e1000e >> - Intel 82574L with DPDK >> - Realtek RTL8111/8168/8411 PCI Express with default driver r8169 >> >> There were two paths connected to the DUT, e.g. Path 1 and Path 2. >> So by default Path 1 had been used. When Path 1 was disconnected, the >> time it took to switch to Path 2 had been measured by counting the lost >> packets. >> Several tests have been conducted and the median calculated. >> >> Terminology: >> >> Median FF: Median fast failover time / ms >> Median LP: Median lost packets / packet(s) >> >> Median FF Median LP >> >> DPDK 1700 3363 >> Intel 350 690 >> Realtek 350 695 >> >> Anyone an idea why DPDK is so "slow"? >> >> Best regards, >> Stefan. > > Hey Stefan, > > A couple of questions regarding your setup which will hopefully help > me figure out what the issue is. > > - Are you just running in active backup mode or are you using one of > the other bonding modes. > - What is down stream of the DUT, is it a switch or are you just > directly connected to another system? > > I'm not sure if the 82574L has LSC interrupt support in DPDK, I'll > check that out, but if it doesn't the PMD need will be polling the > link status which could be slowing down detection of the link going > down and the fail over to the over port. > > Declan > > Hi Declan, regarding your first question I think that I use the active backup mode, but I didn't define anything special. What I did was starting OpenvSwitch with DPDK using following command(s): # Start OVS with DPDK portion using 2GB of node 0 memory ./ovs/vswitchd/ovs-vswitchd --dpdk -c 0xf -n 4 --socket-mem 2048,0 -- unix:/usr/local/var/run/openvswitch/db.sock --pidfile --detach Afterwards I added the interfaces which have been bound to the igb_uio driver as "dpdk interfaces": ./ovs/utilities/ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk sleep 0.5 ./ovs/utilities/ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk sleep 0.5 ./ovs/utilities/ovs-vsctl add-port br0 dpdk2 -- set Interface dpdk2 type=dpdk sleep 0.5 The downstream of the DUT is connected to another switch. Here is a network diagram: http://abload.de/img/ff_testbed_dpdk28sah.png whereby al40-118 is the DUT, al40-115 the sender and al40-111 the receiver. Thanks very much. Stefan.