From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by dpdk.org (Postfix) with ESMTP id E066A156 for ; Sun, 15 Dec 2013 07:38:05 +0100 (CET) Received: by mail-pb0-f46.google.com with SMTP id md12so4208532pbc.33 for ; Sat, 14 Dec 2013 22:39:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Hy8pjEXJA2yK96fkDbO0tHvZIPochq3Hn0Y/7psF/EM=; b=jDmVKoLGAFJIYvdO+3zyQ8A7aRUkF7zG7/Z2UON3sbhY9jKrdj0mY2mXsibYi1ORRD fqO8849UV7vSPdkKUwC57UQN0Pw7la/v5PcVhDy0bGyU8o5BLTdJFQa8dtU5fhnrWt5D kbhheWE1doIDGdFT8B7LuIb6LfPWslQ/ybwji6GPXRKNbMibyYLYyNwMjLojcgVved5p t9ZAMVSK3UIi0ecYKLM1Xykgjq1kQ/WSyGfRAyxNb6fRJFTX98jde/oKveA3Wpbquyfq WXnRk4DOX+Auq9o1cWYVN6tWP3gEZ+BrhCebpX/KUyL08X1cU1PSOerIIveYo5/bjS3u WuLA== MIME-Version: 1.0 X-Received: by 10.68.196.164 with SMTP id in4mr13067481pbc.128.1387089551017; Sat, 14 Dec 2013 22:39:11 -0800 (PST) Received: by 10.68.226.9 with HTTP; Sat, 14 Dec 2013 22:39:10 -0800 (PST) In-Reply-To: References: <52AB3176.7040800@windriver.com> Date: Sun, 15 Dec 2013 12:09:10 +0530 Message-ID: From: Jyotiswarup Raiturkar To: Romulo Rosa Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [dpdk-ovs] Problem with OVS 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: Sun, 15 Dec 2013 06:38:06 -0000 Hi Romulo You can check lib/librte_eal/common/include/rte_pci_dev_ids.h for supported NICs. Also from your pci_unbind status , does not look like any NIC is bound to igb_uio.. On Sat, Dec 14, 2013 at 9:24 PM, Romulo Rosa wrote: > Thanks Paul, > > But i think my NICS are not supportted by Intel DPDK. In this link they a= re > not listed http://dpdk.org/doc/nics. Anyone know if there are other > supported cards? > > ./tools/pci_unbind.py --status > > Network devices using IGB_UIO driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > Network devices using kernel driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:03:00.0 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=3Deth0 > *drv=3Dtg3* unused=3D > *Active* > 0000:03:00.1 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=3Deth1 *drv=3Dt= g3* > unused=3D > 0000:03:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=3Deth2 *drv=3Dt= g3* > unused=3D > 0000:03:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=3Deth3 *drv=3Dt= g3* > unused=3D > 0000:07:00.0 'OneConnect 10Gb NIC (be3)' if=3Deth4* drv=3Dbe2net* unused= =3D > 0000:07:00.1 'OneConnect 10Gb NIC (be3)' if=3Deth5 *drv=3Dbe2net* unused= =3D > > Other network devices > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > 2013/12/13 Paul Barrette > > > > > On 12/12/2013 05:25 PM, Romulo Rosa wrote: > > > >> Hi, > >> > >> i'm tryin to run OVS and i get a error. In documentation was mentioned= a > >> possible solution for this problem but it didnt work to me. Someone ha= ve > >> any idea how to solve this problem? > >> The uio module is loaded. > >> > >> *Command: *./datapath/dpdk/build/ovs_dpdk -c 0xf -n 4 -- -p 0xc > >> > > I think you have the wrong port mask. Try using -p 0x3. > > > > Pb > > > >> -n 2 -k 2 > >> --stats=3D1 --vswitchd=3D0 --client_switching_core=3D1 > >> --config=3D"(0,0,2),(1,0,3)" > >> > >> *Error: * > >> > >> EAL: Core 2 is ready (tid=3D43fd700) > >> EAL: Core 3 is ready (tid=3D3bfc700) > >> EAL: Core 1 is ready (tid=3D4bfe700) > >> WARNING: requested port 2 not present - ignoring > >> WARNING: requested port 3 not present - ignoring > >> config =3D 16,0,2 > >> config =3D 17,0,3 > >> nb_cfg_params =3D 2 > >> Creating mbuf pool 'MProc_pktmbuf_pool' [14336 mbufs] ... > >> HASH: Enabling CRC32 instruction for hashing > >> APP: memzone address is 2ef33980 > >> EAL: Error - exiting with code: 1 > >> Cause: Cannot allocate memory for port tx_q details > >> > >> Thanks! > >> > > > > > > > -- > R=F4mulo Rosa Furtado >