DPDK usage discussions
 help / color / mirror / Atom feed
From: "Sawant, Sunil (Artesyn)" <Sunil.Sawant@Artesyn.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] KNI optimization techniques
Date: Mon, 17 Apr 2017 13:17:17 +0000	[thread overview]
Message-ID: <HK2PR01MB1297B6A2626944B5408690778E060@HK2PR01MB1297.apcprd01.prod.exchangelabs.com> (raw)

Hi,

Requirement - Looking for KNI optimization techniques to speed-up packet transfer from DPDK Port to it corresponding Ethernet interface ( further to DHCP server on Host machine).

Case - DSPs, while booting, try to fetch the boot image on the Host machine. They use TFTP protocol to boot. Now, DSPs fail to boot as the DHCP DISCOVER packets sent by DSPs are delayed over KNI. From the time, the DISCOVER is generated to the time the host sends DHCP OFFERs to the DSPs, a huge time delay is observed (~ 4s).
The boot process works fine without DPDK.

Environment - DPDK 2.1.0 on RHEL 6.4, 64 bit, 8 cores.

Other details -
MemTotal:       32961560 kB
MemFree:        23676720 kB
isolcpus=3,5,7 default_hugepagesz=1G hugepagesz=1G hugepages=8

Optimizations done -

*        Increased Hugepage size

*        Isolated CPU cores

*        Tweaked BIOS parameters - http://dpdk.org/doc/guides-16.04/linux_gsg/nic_perf_intel_platform.html

*        Having multiple kthread for each port

*        Making KNI threads RT and having highest priority

The delay is persistent even after all the above optimizations are done. Could anyone please suggest more/better optimizations ? Is there any way where KNI just transmits the packets the moment it receives (without buffering ) ?

Thanks,
Sunil D. Sawant

             reply	other threads:[~2017-04-17 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 13:17 Sawant, Sunil (Artesyn) [this message]
2017-04-17 15:32 ` Stephen Hemminger

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=HK2PR01MB1297B6A2626944B5408690778E060@HK2PR01MB1297.apcprd01.prod.exchangelabs.com \
    --to=sunil.sawant@artesyn.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).