DPDK usage discussions
 help / color / mirror / Atom feed
From: James Bensley <jwbensley@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] PktGen Ethertype
Date: Wed, 10 May 2017 10:12:48 +0100	[thread overview]
Message-ID: <CAAWx_pX6U+XHJXTpFaKW7aDC7d+18qZaU5h-FEqSSUPRX0f3fA@mail.gmail.com> (raw)
In-Reply-To: <E184B7C6-5466-4CED-BEA7-E1E97C89FBCB@net.in.tum.de>

On 9 May 2017 at 15:13, Paul Emmerich <emmericp@net.in.tum.de> wrote:

Hi Paul,

> https://github.com/emmericp/MoonGen

> You can have a look at one of the example scripts to see packet modifications in action:
>
> https://github.com/emmericp/MoonGen/blob/master/examples/l3-load-latency.lua
>
> Basically, you can add
>
>    pkt.eth.type = <ethertype> (network byte order)
> or
>    pkt.eth:setType(<ethertype>) (automatic byte order swap)
>
> In the main loop at line 92 where it currently modifies the IP addresses.
> This is still fast because we dynamically build and compile the necessary structs for the protocol stack.
>
> You can also receive packets to find out which ethertypes are dropped (if any), an example of packet reception can be found in this example:
> https://github.com/emmericp/MoonGen/blob/master/examples/quality-of-service-test.lua#L108

I've had my eye on MoonGen already and I was reading the doc's trying
to work out how to do the same with MoonGen and PtkGen. I was still
reading the MoonGen docs though so you've saved me some time!.

That last point about checking which packets were received is critical.

Thanks, I'll give this a go!

Cheers,
James.

  reply	other threads:[~2017-05-10  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  8:55 James Bensley
2017-05-09 13:56 ` Wiles, Keith
2017-05-09 14:13   ` Paul Emmerich
2017-05-10  9:12     ` James Bensley [this message]
2017-05-10  9:09   ` James Bensley
2017-05-10 13:53     ` Wiles, Keith

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=CAAWx_pX6U+XHJXTpFaKW7aDC7d+18qZaU5h-FEqSSUPRX0f3fA@mail.gmail.com \
    --to=jwbensley@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).