DPDK patches and discussions
 help / color / mirror / Atom feed
From: James Yu <ypyu2011@gmail.com>
To: "Jayakumar, Muthurajan" <muthurajan.jayakumar@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] send/receive L2 packets from SR-IOV ports using l2fwd-vf
Date: Sat, 11 Jan 2014 20:13:10 -0800	[thread overview]
Message-ID: <CAFMB=kDT9=YYH6m1qwXeq9LZzjZ8B-ZAFxAvwD+4HcXAKnVC=Q@mail.gmail.com> (raw)
In-Reply-To: <5D695A7F6F10504DBD9B9187395A21797C6D013E@ORSMSX103.amr.corp.intel.com>

Jayakumar,

Thanks for pointing this out.

I was using l2fwd in DPDK 1.3.1r2 but could not consistently passing one
directional traffic. I have the following question when using l2fwd:
1. Can I kill the l2fwd using ctrl-c on linux command and restart it again
? Would it be gracefully shutting it down ?
2. If I reboot the VM, would that recover the SR-IOV ?
3. Do I have to issue any commands on the guest or host, or reboot the host
after I restart l2fwd to make the SR-IOV work again ?

Sometime I could pass traffic one directional from Spirent. The traffic was
sent to port 1 and received on port 2. But the other direction sending
traffic to port 2, however, did not receive traffic on port 1.

I have posted the description and setup on the other email thread with this
title "[dpdk-dev] one directional traffic from SR-IOV port using l2fwd". If
you know how to make bi-directional traffic work, please reply to that
email thread.

Thanks.

James



On Fri, Jan 10, 2014 at 9:13 PM, Jayakumar, Muthurajan <
muthurajan.jayakumar@intel.com> wrote:

> James,
>
> You are right.
>
> From 1.3 release, the L2 Forwarding sample application (chapter 8.0 in 1.3
> DPDK Sample Application User Guide) indicates that L2fwd and L2fwd-vf have
> been merged into one L2 sample application example.
>
> (The Sample Application guide introduction referring the merge)
>
> The L2 Forwarding sample application is a simple example of packet
> processing using Intel(r) Data Plane Development Kit (Intel(r) DPDK) which
> also takes advantage of Single Root I/O Virtualization (SR-IOV) features in
> a virtualized environment.
> Note: Please note that previously a separate L2 Forwarding in Virtualized
> Environments sample application was used, however, in later Intel(r) DPDK
> versions these sample applications have been merged
>
> Thanks,
> M Jay
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of James Yu
> Sent: Friday, January 10, 2014 8:32 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] send/receive L2 packets from SR-IOV ports using
> l2fwd-vf
>
> I found that it used to have l2fwd-vf in DPDK 1.2.3 release (
> http://www.dpdk.org/browse/dpdk/tree/examples/l2fwd-vf/main.c?h=1.2.3)
> But in the next release 1.3.1, that directory is gone. Does that mean it
> is merged to some other tool ? Which tool can I use to send/receive L2
> traffic from SR-IOV ports.
>
> In DPDK 1.3.1r2, to use use SR-IOV ports, should I use l2fwd-vf from 1.2.3
> release or simply use l2fwd ?
>
> Thanks
>
> James
>

      reply	other threads:[~2014-01-12  4:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11  4:31 James Yu
2014-01-11  5:13 ` Jayakumar, Muthurajan
2014-01-12  4:13   ` James Yu [this message]

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='CAFMB=kDT9=YYH6m1qwXeq9LZzjZ8B-ZAFxAvwD+4HcXAKnVC=Q@mail.gmail.com' \
    --to=ypyu2011@gmail.com \
    --cc=dev@dpdk.org \
    --cc=muthurajan.jayakumar@intel.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).