From: Matthew Hall <mhall@mhcomputing.net>
To: "Vass, Sandor (Nokia - HU/Budapest)" <sandor.vass@nokia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] VMXNET3 on vmware, ping delay
Date: Thu, 25 Jun 2015 08:18:34 -0700 [thread overview]
Message-ID: <20150625151834.GA29296@mhcomputing.net> (raw)
In-Reply-To: <792CF0A6B0883C45AF8C719B2ECA946E42B2430F@DEMUMBX003.nsn-intra.net>
On Thu, Jun 25, 2015 at 09:14:53AM +0000, Vass, Sandor (Nokia - HU/Budapest) wrote:
> According to my understanding each packet should go
> through BR as fast as possible, but it seems that the rte_eth_rx_burst
> retrieves packets only when there are at least 2 packets on the RX queue of
> the NIC. At least most of the times as there are cases (rarely - according
> to my console log) when it can retrieve 1 packet also and sometimes only 3
> packets can be retrieved...
By default DPDK is optimized for throughput not latency. Try a test with
heavier traffic.
There is also some work going on now for DPDK interrupt-driven mode, which
will work more like traditional Ethernet drivers instead of polling mode
Ethernet drivers.
Though I'm not an expert on it, there is also a series of ways to optimize for
latency, which hopefully some others could discuss... or maybe search the
archives / web site / Intel tuning documentation.
Matthew.
next prev parent reply other threads:[~2015-06-25 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 9:14 Vass, Sandor (Nokia - HU/Budapest)
2015-06-25 15:18 ` Matthew Hall [this message]
2015-06-25 15:46 ` Avi Kivity
2015-06-25 16:37 ` Matthew Hall
2015-06-25 18:44 ` Thomas Monjalon
2015-06-25 18:54 ` Matthew Hall
2015-06-25 19:20 ` Avi Kivity
2015-06-25 20:56 ` Patel, Rashmin N
2015-06-25 21:13 ` Vass, Sandor (Nokia - HU/Budapest)
2015-06-25 22:36 ` Matthew Hall
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=20150625151834.GA29296@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=sandor.vass@nokia.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).