DPDK usage discussions
 help / color / mirror / Atom feed
From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: Saurabh Mishra <saurabh.globe@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] DPDK i40evf problem in receving packet
Date: Wed, 10 Feb 2016 16:00:24 +0500	[thread overview]
Message-ID: <CAN7yQ2p7dATF+dJYW7aqmgbaiYnKbh0ma62idGOeUDeUKLotGQ@mail.gmail.com> (raw)
In-Reply-To: <CAMnwyJ3t7x_jZ5=kKsM+D2SJitD3bi3hVWwSrfbTiCfjd46SKA@mail.gmail.com>

Hi Saurabh,
Can you tell me what card you are uing


*Regards:*
Zain ul Abideen


*Disclaimer**: The information contained in this e-mail and any attachments
is confidential; it is intended only for use of the individual or entity
named above. If the reader of this message is not the intended recipient,
you are notified that any dissemination, distribution or use of this
information is strictly prohibited. If you have received this communication
in error, please delete it and email confirmation to the sender. Thank You.*


On Wed, Feb 10, 2016 at 6:30 AM, Saurabh Mishra <saurabh.globe@gmail.com>
wrote:

> Hi Qian --
>
> Any suggestions? This is bit urgent.
>
> /Saurabh
>
> On Sat, Feb 6, 2016 at 9:22 AM, Saurabh Mishra <saurabh.globe@gmail.com>
> wrote:
>
> > Hi Qian --
> >
> >
> > Here's the data from Host:
> >
> > [root@oscompute3 ~]# ethtool -i p3p1
> >
> > driver: i40e
> >
> > version: 1.0.11-k
> >
> > firmware-version: f4.40 a1.4 n04.53 e80001dc0
> >
> > bus-info: 0000:04:00.0
> >
> > supports-statistics: yes
> >
> > supports-test: yes
> >
> > supports-eeprom-access: yes
> >
> > supports-register-dump: yes
> >
> > supports-priv-flags: no
> >
> > [root@oscompute3 ~]# ethtool -i p3p2
> >
> > driver: i40e
> >
> > version: 1.0.11-k
> >
> > firmware-version: f4.40 a1.4 n04.53 e80001dc0
> >
> > bus-info: 0000:04:00.1
> >
> > supports-statistics: yes
> >
> > supports-test: yes
> >
> > supports-eeprom-access: yes
> >
> > supports-register-dump: yes
> >
> > supports-priv-flags: no
> >
> > [root@oscompute3 ~]#
> >
> > EthApp> drvinfo
> >
> > Port 0 driver: rte_i40evf_pmd (ver: RTE 2.2.0)
> >
> > Port 1 driver: rte_i40evf_pmd (ver: RTE 2.2.0)
> >
> > EthApp>
> >
> > On Fri, Feb 5, 2016 at 4:59 PM, Xu, Qian Q <qian.q.xu@intel.com> wrote:
> >
> >> What's your current firmware info, can u run ethtool -i port_interface
> to
> >> check?
> >>
> >> Thanks
> >> Qian
> >>
> >> -----Original Message-----
> >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Saurabh Mishra
> >> Sent: Saturday, February 06, 2016 6:33 AM
> >> To: dev@dpdk.org; users@dpdk.org
> >> Subject: [dpdk-dev] DPDK i40evf problem in receving packet
> >>
> >> Hi,
> >>
> >> I'm seeing two problems:
> >>
> >> 1)  when use our kernel '3.10.88-8.0.0.0.6', we only receive first
> >> packet but not subsequent ones at all after that. However, when I use
> >> centos7.0, then l2fwd is able to receive all the packets.
> >>
> >> 2) I've also seen that on centos7.0, symmetric_mp itself is not working.
> >> dev start fails with 280 error.
> >>
> >> i40evf is giving us lot of headache. The i40evf kernel driver works
> >> without any problem. Host is a centos7 KVM. I've already upgraded
> firmware
> >> to latest.
> >>
> >> [root@localhost ~]# uname -a
> >>
> >> Linux localhost.localdomain 3.10.0-327.4.5.el7.x86_64 #1 SMP Mon Jan 25
> >> 22:07:14 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> >>
> >> [root@localhost ~]#
> >>
> >> [root@localhost ~]# ./symmetric_mp fakeelf --file-prefix=virtaddr -c2
> >> -m2048 -n1 --base-virtaddr=0x7fa000000000 --proc-type=primary -- -p 3
> >> --num-procs=1 --proc-id=0
> >>
> >> EAL: Detected lcore 0 as core 0 on socket 0
> >>
> >> EAL: Detected lcore 1 as core 0 on socket 0
> >>
> >> EAL: Support maximum 128 logical core(s) by configuration.
> >>
> >> EAL: Detected 2 lcore(s)
> >>
> >> EAL: No free hugepages reported in hugepages-1048576kB
> >>
> >> EAL: VFIO modules not all loaded, skip VFIO support...
> >>
> >> EAL: Setting up physically contiguous memory...
> >>
> >> EAL: Ask a virtual area of 0x2a800000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa000000000 (size = 0x2a800000)
> >>
> >> EAL: Ask a virtual area of 0x200000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa02a800000 (size = 0x200000)
> >>
> >> EAL: Ask a virtual area of 0x54000000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa02aa00000 (size = 0x54000000)
> >>
> >> EAL: Ask a virtual area of 0x400000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07ea00000 (size = 0x400000)
> >>
> >> EAL: Ask a virtual area of 0x200000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07ee00000 (size = 0x200000)
> >>
> >> EAL: Ask a virtual area of 0x200000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07f000000 (size = 0x200000)
> >>
> >> EAL: Ask a virtual area of 0x600000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07f200000 (size = 0x600000)
> >>
> >> EAL: Ask a virtual area of 0x200000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07f800000 (size = 0x200000)
> >>
> >> EAL: Ask a virtual area of 0x200000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07fa00000 (size = 0x200000)
> >>
> >> EAL: Ask a virtual area of 0x400000 bytes
> >>
> >> EAL: Virtual area found at 0x7fa07fc00000 (size = 0x400000)
> >>
> >> EAL: Requesting 1024 pages of size 2MB from socket 0
> >>
> >> EAL: TSC frequency is ~2600000 KHz
> >>
> >> EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
> >> unreliable clock cycles !
> >>
> >> EAL: Master lcore 1 is ready (tid=3e55900;cpuset=[1])
> >>
> >> EAL: PCI device 0000:00:09.0 on NUMA socket -1
> >>
> >> EAL:   probe driver: 8086:154c rte_i40evf_pmd
> >>
> >> EAL:   PCI memory mapped at 0x7fa080000000
> >>
> >> EAL:   PCI memory mapped at 0x7fa080010000
> >>
> >> EAL: PCI device 0000:00:0a.0 on NUMA socket -1
> >>
> >> EAL:   probe driver: 8086:154c rte_i40evf_pmd
> >>
> >> EAL:   PCI memory mapped at 0x7fa080014000
> >>
> >> EAL:   PCI memory mapped at 0x7fa080024000
> >>
> >> # Initialising port 0... Queue :1
> >>
> >> PMD: i40e_dev_rx_queue_setup(): Rx Burst Bulk Alloc Preconditions are
> >> satisfied. Rx Burst Bulk Alloc function will be used on port=0, queue=0.
> >>
> >> PMD: i40e_set_tx_function_flag(): Vector tx can be enabled on this txq.
> >>
> >> PMD: i40e_set_rx_function(): Port[0] doesn't meet Vector Rx
> preconditions
> >>
> >> PMD: i40e_set_rx_function(): Rx Burst Bulk Alloc Preconditions are
> >> satisfied. Rx Burst Bulk Alloc function will be used on port=0.
> >>
> >> PMD: i40e_set_tx_function(): Simple tx finally be used.
> >>
> >> smp_port_init() dev start error 280
> >>
> >> EAL: Error - exiting with code: 1
> >>
> >>   Cause: Error initialising ports
> >>
> >> [root@localhost ~]#
> >>
> >
> >
>

  reply	other threads:[~2016-02-10 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 22:32 [dpdk-users] " Saurabh Mishra
2016-02-06  0:59 ` [dpdk-users] [dpdk-dev] " Xu, Qian Q
2016-02-06 17:22   ` Saurabh Mishra
2016-02-10  1:30     ` Saurabh Mishra
2016-02-10 11:00       ` Muhammad Zain-ul-Abideen [this message]
2016-02-10 11:15         ` Thomas Monjalon
2016-02-10 21:44           ` Saurabh Mishra

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=CAN7yQ2p7dATF+dJYW7aqmgbaiYnKbh0ma62idGOeUDeUKLotGQ@mail.gmail.com \
    --to=zain2294@gmail.com \
    --cc=dev@dpdk.org \
    --cc=saurabh.globe@gmail.com \
    --cc=users@dpdk.org \
    /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).