From: ANKIT BATRA <ankitbatra2009@gmail.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Testing vmdq sample application
Date: Thu, 11 Sep 2014 00:30:05 +0530 [thread overview]
Message-ID: <CABh7pOO8OTZudyDezEAwSOXzv3G3fv+1o8teQjrbE65FLr_SZQ@mail.gmail.com> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F96251184E807@shsmsx102.ccr.corp.intel.com>
Hi,
I have started the application on my host machine.And from another terminal
on host machine gave sudo killall -HUP vmdq_dcb_app and sent packets on NIC
card from another machine .But on terminal where vmdq application is
running, I am seeing that no packets are coming.All rows and columns are
0.And where will the VMs will come into picture here for testing this.
Please suggest and correct me if i am doing anything incorrect.
On Wed, Sep 10, 2014 at 6:24 AM, Ouyang, Changchun <
changchun.ouyang@intel.com> wrote:
> Hi
>
> Firstly compiling the application
> 1. Go to the examples directory:
> export RTE_SDK=/path/to/rte_sdk
> cd ${RTE_SDK}/examples/vmdq
> 2. Set the target (a default target is used if not specified). For example:
> export RTE_TARGET=x86_64-native-linuxapp-gcc
> See the Intel® DPDK Getting Started Guide for possible RTE_TARGET values.
> 3. Build the application:
> make
>
> Then running the application
> To run the example in a linuxapp environment:
> user@target:~$ ./build/vmdq_app -c f -n 4 -- --nb-pools 8
>
> If you use 1G NIC, 8 pools are available,
> If you use 10G NIC, 64 pools are available,
>
> At last, send packets with vlan tag to select a pool.
>
> The vlan tag and pool has the following mapping:
> const uint16_t vlan_tags[] = {
> 0, 1, 2, 3, 4, 5, 6, 7, // It occupies pool 0 ~ pool
> 7, one for each
> 8, 9, 10, 11, 12, 13, 14, 15, // It occupies pool 8 ~ pool
> 15, one for each
> 16, 17, 18, 19, 20, 21, 22, 23, // It occupies pool 16 ~ pool
> 23, one for each
> 24, 25, 26, 27, 28, 29, 30, 31, // It occupies pool 24 ~ pool
> 31, one for each
> 32, 33, 34, 35, 36, 37, 38, 39, // It occupies pool 32 ~ pool
> 39, one for each
> 40, 41, 42, 43, 44, 45, 46, 47, // It occupies pool 40 ~ pool
> 47, one for each
> 48, 49, 50, 51, 52, 53, 54, 55, // It occupies pool 48 ~ pool
> 55, one for each
> 56, 57, 58, 59, 60, 61, 62, 63, // It occupies pool 56 ~ pool
> 63, one for each
> };
>
> Thanks
> Changchun
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ANKIT BATRA
> > Sent: Wednesday, September 10, 2014 3:23 AM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] Testing vmdq sample application
> >
> > Hi,
> >
> > I am trying to run vmdq sample application.But not getting how to test
> > this.Can anyone please help with detailed procedure how to test this
> sample
> > application.
> > --
> > Regards
> > Ankit Batra
>
--
Regards
Ankit Batra
next prev parent reply other threads:[~2014-09-10 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 19:23 ANKIT BATRA
2014-09-10 0:54 ` Ouyang, Changchun
2014-09-10 19:00 ` ANKIT BATRA [this message]
2014-09-10 19:48 ` Wei-Chun Chao
2014-09-11 8:33 ` Richardson, Bruce
2014-09-11 10:58 ` ANKIT BATRA
2014-09-12 6:51 ` Wei-Chun Chao
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=CABh7pOO8OTZudyDezEAwSOXzv3G3fv+1o8teQjrbE65FLr_SZQ@mail.gmail.com \
--to=ankitbatra2009@gmail.com \
--cc=changchun.ouyang@intel.com \
--cc=dev@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).