From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Network - Drivers
Date: Wed, 14 Dec 2016 10:52:38 +0100 [thread overview]
Message-ID: <2724477.26M6RAmHcu@xps13> (raw)
In-Reply-To: <0E45546B-1C54-4673-B932-867C6ED6683F@cloudsimple.com>
Hi,
2016-12-14 15:08, Kumaraparameshwaran Rathnavel:
> Hi All,
>
> I have been trying to use network drivers provided by the DPDK to write a small client - server application. I will explain the configuration
I suggest to start your tests with testpmd in txonly mode.
> I used uio_pci_generic and igb_uio both modules in the Kernel for DPDK Network drivers in userspace. The client and server were run on Centos VM with virtual box as the Host and made sure that Virtual NIC had the driver.
>
> The sequence of calling the functions as
>
> rte_eth_dev_count
> rte_eth_dev_configure
> tx_queue_setup
> rte_pkt_mbuf_alloc
>
> I filled the packet with Ethernet Header and Ethertype as 0x8870. I did fill the pkt_len and l2_hdr len. I did not fill the VLAN Tag, Outer VLAN tag,
> flags. Transmission is showing success but I am not receiving any packet in the other side wheree i run the receiver setup.
>
> Can you suggest what should be done and how it should be done.
>
> Does Drivers work in Virtual Box? If not which is prefered ESX or KVM and does Virtual NICs work?
The supported NICs are listed here: http://dpdk.org/doc/nics
Virtualbox is not known to be fully compatible, but virtio works with Qemu/KVM
and vmxnet3 works with ESX.
next prev parent reply other threads:[~2016-12-14 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 9:38 Kumaraparameshwaran Rathnavel
2016-12-14 9:52 ` Thomas Monjalon [this message]
2016-12-14 10:02 ` Kumaraparameshwaran Rathnavel
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=2724477.26M6RAmHcu@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=krath@cloudsimple.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).