From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by dpdk.org (Postfix) with ESMTP id 05F92156 for ; Thu, 2 Jan 2014 11:19:07 +0100 (CET) Received: by mail-vc0-f182.google.com with SMTP id lc6so7176507vcb.13 for ; Thu, 02 Jan 2014 02:20:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mR5+xi119X0A+/HlKG5zrUZD/xfmijKrBir/J3kxog4=; b=U/DroAaAU52hRzT6wmVByar1uODru9Dx0PR3xWWNrMei1fYeU1XItV1olyCUJn1YCN sDNtu3DoNT/G23HFbLXcb/2VfmxpTQlb/THKZof39uO0zQrT2ulPG1JJD/v6i33Jdh12 cTEB08FfP2aDteTtO461dbwSABf0hQ5OzXFQAQb4UnNILzYZpBk8IpHfE/Vf5BsNAfSm MxThFxDBKCc3jB6KHDJEhhTMJmCGmGNx9y6ts92bEYJapmTdpDTWPJ0AXu0frz3K2J75 TbjizvJdeDZlG4peMkrJ/DS1ZH6cj+VR00rGpAo9tGbKAfRgHgBRCcZ8ETdhrLlQiWwD e7mA== X-Gm-Message-State: ALoCoQkyFu4Lil3GKOl1sBdLCn9aH7Fgv7YShvo4tZmBFoUf2BkyeJHztNbJTfnSu7JfPBBpG0k8 MIME-Version: 1.0 X-Received: by 10.220.252.71 with SMTP id mv7mr39653vcb.68.1388658018386; Thu, 02 Jan 2014 02:20:18 -0800 (PST) Received: by 10.58.41.99 with HTTP; Thu, 2 Jan 2014 02:20:18 -0800 (PST) X-Originating-IP: [109.64.120.65] In-Reply-To: References: Date: Thu, 2 Jan 2014 12:20:18 +0200 Message-ID: From: Daniel Kaminsky To: cr singh Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] regarding KNI 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, 02 Jan 2014 10:19:08 -0000 Hi C R, This is a limitation of the KNI example and not of the DPDK package. The current KNI example can use one core for single task - Egress/Ingress on one port. You definitely can change it, look into *main_loop *function. Regards, Daniel Kaminsky On Thu, Jan 2, 2014 at 11:32 AM, cr singh wrote: > hello devs, > > I am using DPDK 1.5.0 and trying to use KNI interface to measure throughput > through it > > > > ------------------------------------------------------------------------------------------------------------ > I have machine with 2 lcores and 2 physical interface, and in running kni > sample application --config parameter we are supposed to give > 1)port no, > 2)lcore_rx, > 3)lcore_tx, right? > > so can it be possible to give same lcore no. for both ports, like > > kni -c 0x3 -n 4 -- -P -p 0x3 --config"(0,0,1),(1,0,1)" > > As i have tried and after running this two interface vEth0 and vEth1 is > created, but when i am giving ip with ifconfig to vEth1 then it is showing > the below message ... > > SIOCSIFFLAGS: Timer expired, > > while i am able to bring up the the vEth0 interface successfully. > > > ----------------------------------------------------------------------------------------------------- > i am pasting some details which prints while running the application ... > > Checking link status > .....done > Port 0 Link Up - speed 1000 Mbps - full-duplex > Port 1 Link Up - speed 1000 Mbps - full-duplex > APP: Lcore 1 is writing to port 0 > APP: Lcore 0 is reading from port 0 > > > and here in last two line Lcore 1 and Lcore 0 is writting and reading for > port 0 and may be therefore i am able to bring up the vEth0. and there is > no core for port 1 so it is failing. > > > --------------------------------------------------------------------------------------------------------- > > So my question is why can't we use same lcores for reading and writing for > both ports, does DPDK restricts using same lcores for 2 ports (as it > seems), and if so, then why?? > > > > Thanks in advance > C R >