DPDK usage discussions
 help / color / mirror / Atom feed
From: "VERDOUX, Sylvain" <s.verdoux@evs.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
	Paul Emmerich <emmericp@net.in.tum.de>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Howto control sending IFG
Date: Wed, 16 Nov 2016 07:53:51 +0000	[thread overview]
Message-ID: <294AEAFC4B0A3E498038549EC65E9D1B018AB0A221@BELGSMBX01.EVS.TV> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA6129B2A47@IRSMSX102.ger.corp.intel.com>

Thank you both for the link to moongen, i did not see it during my research and it seems the project is exactly studying what I'm facing. Moongen in its software solution is filling gaps sending invalid packets. I'm not sure I can go with that solution but it is worth testing.

Best Regards,

Sylvain

-----Message d'origine-----
De : Van Haaren, Harry [mailto:harry.van.haaren@intel.com] 
Envoyé : mardi 15 novembre 2016 16:11
À : VERDOUX, Sylvain; users@dpdk.org
Objet : RE: Howto control sending IFG

> From: users [mailto:users-bounces@dpdk.org] On Behalf Of VERDOUX, 
> Sylvain
> Sent: Tuesday, November 15, 2016 2:31 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Howto control sending IFG
> 
> Hi,
> 
> Using i40e pmd i'm currently trying to control precisely packets 
> emission rate. When dealing with an IFG (inter frame gap) of 1ms it 
> works fine, but dealing with IFG under 100us I'm seeing bursts on the 
> receiver. I was wondering if there was a better way to be close to the 
> wanted IFG instead of waiting and using rte_eth_tx_burst with 1 packet 
> at a time. I did not see anything relevant in mbuf structure, and I was wondering if tx queue threshold could help, but I'm not sure to understand well the impact of those thresholds.
> Any advice is welcome :)
> 
> Best Regards,
> Sylvain


Hi Sylvain,

I don't personally have experience, however the MoonGen traffic generator has a few solutions to this problem; I can recommend reading their documentation on rate control[1], and the paper they wrote on the topic[2].

Hopefully that leads you to a solution, -Harry

[1] https://github.com/emmericp/MoonGen#rate-control
[2] https://www.net.in.tum.de/fileadmin/bibtex/publications/papers/MoonGen_IMC2015.pdf

      reply	other threads:[~2016-11-16  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 14:30 VERDOUX, Sylvain
2016-11-15 14:56 ` Paul Emmerich
2016-11-15 15:10 ` Van Haaren, Harry
2016-11-16  7:53   ` VERDOUX, Sylvain [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=294AEAFC4B0A3E498038549EC65E9D1B018AB0A221@BELGSMBX01.EVS.TV \
    --to=s.verdoux@evs.com \
    --cc=emmericp@net.in.tum.de \
    --cc=harry.van.haaren@intel.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).