From: Marc Sune <marcdevel@gmail.com>
To: Vivek Gupta <vivek-g@hcl.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Port 0 Link Down - L2fwd sample application
Date: Thu, 7 Apr 2016 14:57:15 +0200 [thread overview]
Message-ID: <CA+3n-Trn1rqyZf3W0=GmtWV3=5Cp57ekKOsG8rE2Haqin9MkvQ@mail.gmail.com> (raw)
In-Reply-To: <488FF59D9020184C9DCF4B4A0DA478142554AD92@NDA-HCLT-MBS03.hclt.corp.hcl.in>
2016-04-07 14:50 GMT+02:00 Vivek Gupta <vivek-g@hcl.com>:
> Hi
>
> I have binded eth0 and eth1 with DPDK and then tried to run the l2fwd
> example as below
>
> ./build/l2fwd -c f -n 4 -- -q 8 -p 0x11 but each time I get error
> *****************************
> Checking link status..............
> Port 0 Link Down
> Port 1 Link Down
> ********************************************
>
> I tried with test-pmd example but same result.Could you please help to up
> the link?
>
> Port status is as below-
> Network devices using DPDK-compatible driver
> ============================================
> 0000:01:00.0 'Ethernet Controller 10-Gigabit X540-AT2' drv=uio_pci_generic
> unused=igb_uio
> 0000:01:00.1 'Ethernet Controller 10-Gigabit X540-AT2' drv=uio_pci_generic
> unused=igb_uio
> 0000:06:00.0 'Ethernet Controller 10-Gigabit X540-AT2' drv=uio_pci_generic
> unused=igb_uio
> 0000:06:00.1 'Ethernet Controller 10-Gigabit X540-AT2' drv=uio_pci_generic
> unused=igb_uio
>
> Network devices using kernel driver
> ===================================
> 0000:81:00.0 'Ethernet Controller 10-Gigabit X540-AT2' if=eth4 drv=ixgbe
> unused=igb_uio,uio_pci_generic
> 0000:81:00.1 'Ethernet Controller 10-Gigabit X540-AT2' if=eth5 drv=ixgbe
> unused=igb_uio,uio_pci_generic
>
> Other network devices
> =====================
> <none>
>
>
> Thanks & Regards
> Vivek Gupta
>
In which commit or version are you?
Marc
>
>
> ::DISCLAIMER::
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as
> information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in
> transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability
> on the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the
> author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior
> written consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error
> please delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses
> and other defects.
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>
next prev parent reply other threads:[~2016-04-07 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 12:50 Vivek Gupta
2016-04-07 12:57 ` Marc Sune [this message]
2016-04-07 13:18 ` Vivek Gupta
2016-04-08 1:21 ` Lu, Wenzhuo
2016-04-08 2:42 ` Jianbo Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+3n-Trn1rqyZf3W0=GmtWV3=5Cp57ekKOsG8rE2Haqin9MkvQ@mail.gmail.com' \
--to=marcdevel@gmail.com \
--cc=dev@dpdk.org \
--cc=vivek-g@hcl.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).