From: xiaozhe shao <sxz1069@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Using 1Gbps NIC to send packets, but only get 100Mbps speed
Date: Tue, 20 Sep 2016 11:09:36 -0400 [thread overview]
Message-ID: <E13FFCE6-FA29-46C7-AA94-2EC77FE52D9D@gmail.com> (raw)
Hi all,
I’m sending packet by rte_eth_tx_burst() function. With 1Gbps NIC, I just get 100Mbps speed.
I use the following code to send packets (In order to send packets, I keep calling rte_eth_tx_burst).
for (i=0; i < BURST_SIZE;){
i = i + rte_eth_tx_burst(port, queue, buffer + i, BURST_SIZE - i);
}
My NICs are “Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)” and “Intel Corporation 82576 Gigabit Ethernet Connection (rev 01)”. When I get the link state through DPDK, the link_speed is 1000.
I try testpmd with the instructions of “http://dpdk.org/doc/quick-start <http://dpdk.org/doc/quick-start>”. It works well. No dropped packets.
When I send packets with 60 bits length, the rate is only about 140000 pps. When I send packets with 1500 bits length, the rate is about 8000 pps. I only get 100Mbps sending speed.
My OS is “Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.81-1 x86_64 GNU/Linux”. I tried DPDK-2.2.0 and DPDK-16.07. The results are same.
I also found a strange thing. If I send the packet that has the destination MAC same with the MAC address of the NIC that sends the packet, I can get 1.4Mpps with the 60-bit-length packets.
I profile the sending program with gperf. The “rte_delay_us” consumes more than 90% running time. But I don’t know the caller of “rte_delay_us”. In the output of gperf, “rte_delay_us” is “spontaneous”.
I don’t know why I cannot get 1Gbps send speed. Did anyone meet the similar issue? How to address it?
Best regards,
-xiaozhe
next reply other threads:[~2016-09-20 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 15:09 xiaozhe shao [this message]
2016-09-27 13:41 ` xiaozhe shao
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=E13FFCE6-FA29-46C7-AA94-2EC77FE52D9D@gmail.com \
--to=sxz1069@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).