DPDK patches and discussions
 help / color / mirror / Atom feed
From: wenxu  <wenx05124561@163.com>
To: dev@dpdk.org
Cc: "wenxu@ucloud.cn" <wenxu@ucloud.cn>
Subject: [dpdk-dev] dpdk startup cannot send/recv packet in first serveral seconds
Date: Tue, 18 Jul 2017 14:08:07 +0800 (CST)	[thread overview]
Message-ID: <6c8e5dea.550b.15d544f93ec.Coremail.wenx05124561@163.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 1185 bytes --]

Hi all,

I just test ovs-dpdk with restart. I found when the dpdk start the PHYSICAL NIC can't send/recv packet

I have a vhostuserclient port and dpdk port£¨82599EB£© bridge with br0

It spends 1.4s I restart the ovs-vswitchd.
1.  I send icmp packet(1 packet/second) from virtual machine to outside the host£¬ there are 7 packets lost.
2.  If I send packet to the br0 there are only 2 packets lost(the restart reason). 

For the first case the other 5 packets. The datapath flow also forward to dpdk port, The dpdk port no dropped counter and have 5 tx counter. 
I debug in the ovs-dpdk , the packet have been sent through port and return zero£¨with no dropped), I think it's a problem of dpdk startup

Then I setup a own dpdk program when I start the program.  I also can't send/recv packet in the first 5 seconds when it startup.

Is there some restriction for dpdk startup to send/recv packet on PHYSICAL NIC immediately?

BR
wenxu





 \x16º&Áè³…ª5Š{^•Ê&N牺]|ÓÍ}ÓM´×´^¶êç=«aÁè³…ª5Š{^•Ê&Eç\x1eŠ÷~º&š\x06´Ö)ízW(šh\x1aÓX§µé\¢m}ÛžyÛÏ^[ÉÚ]’Šà>‹-~,pŠØDHÄωÐ\0\x13n7۝ߢ·^½Ú]’ŠàNçµð›¥ÛM{ÓÍ|çß´ÛM\x02\x11$ÑyÇ¢½ç_®‰ŸšÉ kM8~h§µé\¢mt۝öã^[Éù¬š\x06µÓWæŠ{^•Ê&Â+a\x11#\x13?ôËKðÇ\x11\x14€\0D¶ç¡‚1!ÀßÎ5웥ÛM{Û}|çÍ;ÓEÄÆÒ袝u\Šèœú+´\x05D

                 reply	other threads:[~2017-07-18  6:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6c8e5dea.550b.15d544f93ec.Coremail.wenx05124561@163.com \
    --to=wenx05124561@163.com \
    --cc=dev@dpdk.org \
    --cc=wenxu@ucloud.cn \
    /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).