DPDK patches and discussions
 help / color / mirror / Atom feed
From: wei wang <lnykww@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-users] ixgbe drop all the packet
Date: Fri, 2 Sep 2016 11:57:13 +0800	[thread overview]
Message-ID: <CAPM6dUD6A95++Pb_wgVCmn11HsuqM7YYc08E=zU8kzS+RMZ1AA@mail.gmail.com> (raw)
In-Reply-To: <CAPM6dUA1tbpR6vfEaEQt8jfftsuVmmbfx4VieAim5mxBOcAy-A@mail.gmail.com>

The rx function used was ixgbe_recv_pkts_bulk_alloc.

the problem seems that the rx desc ring not full, but nic don't write
data to ring and inc the missed error counter.



2016-09-01 21:48 GMT+08:00 wei wang <lnykww@gmail.com>:
> my enviroment:
> NIC:X540
> DPDK version:2.2.0
>
> problems:
> start dpdk app with traffic not stopped,app can't receive any packet
> from dpdk ixgbe driver (1.2w pps udp packet).
> test five times would happens 1 ~ 2 times.
>
> The stats of the nic (ipackets==3230 and imissed == ierrors):
> ipackets 3230 imissed 9780225 ierrors 9780225
> ipackets 3230 imissed 9792154 ierrors 9792154
> ipackets 3230 imissed 9804310 ierrors 9804310
> ipackets 3230 imissed 9816177 ierrors 9816177
> ipackets 3230 imissed 9828042 ierrors 9828042
> ipackets 3230 imissed 9839694 ierrors 9839694
> ipackets 3230 imissed 9851412 ierrors 9851412
> ipackets 3230 imissed 9863134 ierrors 9863134
> ipackets 3230 imissed 9874722 ierrors 9874722
> ipackets 3230 imissed 9886776 ierrors 9886776
> ipackets 3230 imissed 9898616 ierrors 9898616
> ipackets 3230 imissed 9910648 ierrors 9910648
> ipackets 3230 imissed 9922513 ierrors 9922513
>
> The value of register RDH:1023
> The value of register RDT:959
>
> there are some desc value log for one queue, the format of the log is
> [desc_idx](DD value, vlan, length, status_error) :
> [959]:(0,0, 0, 0) [960]:(1,0, 2048, 1342308425) [961]:(1,0, 2048,
> 1342308425) [962]:(1,0, 1031, 1342308427)
> [963]:(1,0, 0, 3) [964]:(1,0, 0,       3)
> [965]:(1,0, 2048, 1342308425) [966]:(1,0, 2048, 1342308425)
> [967]:(1,0, 1031, 1342308427) [968]:(1,0, 0, 3) [969]:(1,0, 0, 3)
> [970]:(1,0, 2048, 1342308425)
> [971]:(1,0, 2048, 1342308425) [972]:(1,0, 1031, 1342308427)
> [973]:(1,0, 0, 3) [974]:(1,0, 0, 3)
> [975]:(1,0, 2048, 1342308425) [976]:(1,0, 2048, 1342308425)
> [977]:(1,0, 1031, 1342308427) [978]:(1,0, 0, 3)
> [979]:(1,0, 0, 3) [980]:(1,0, 2048, 1342308425) [981]:(1,0, 2048,
> 1342308425) [982]:(1,0, 1031, 1342308427)
> [983]:(1,0, 0, 3) [984]:(1,0, 0, 3) [985]:(1,0, 2048, 1342308425)
> [986]:(1,0, 2048, 1342308425)
> [987]:(1,0, 1031, 1342308427) [988]:(1,0, 0, 3) [989]:(1,0, 0, 3)
> [990]:(1,0, 2048, 1342308425)
> [991]:(1,0, 2048, 1342308425) [992]:(1,0, 1031, 1342308427)
> [993]:(1,0, 0, 3) [994]:(1,0, 0, 3)
> [995]:(1,0, 2048, 1342308425) [996]:(1,0, 2048, 1342308425)
> [997]:(1,0, 1031, 1342308427) [998]:(1,0, 0, 3)
> [999]:(1,0, 0, 3) [1000]:(1,0, 2048, 1342308425) [1001]:(1,0, 2048,
> 1342308425) [1002]:(1,0, 1031, 1342308427)
> [1003]:(1,0, 0, 3) [1004]:(1,0, 0, 3) [1005]:(1,0, 2048, 1342308425)
> [1006]:(1,0, 2048, 1342308425)
> [1007]:(1,0, 1031, 1342308427) [1008]:(1,0, 0, 3) [1009]:(1,0, 0, 3)
> [1010]:(1,0, 2048, 1342308425)
> [1011]:(1,0, 2048, 1342308425) [1012]:(1,0, 1031, 1342308427)
> [1013]:(1,0, 0, 3)[1014]:(1,0, 0, 3)
> [1015]:(1,0, 2048, 1342308425) [1016]:(1,0, 2048, 1342308425)
> [1017]:(1,0, 1031, 1342308427) [1018]:(1,0, 0, 3)
>  [1019]:(1,0, 0, 3) [1020]:(1,0, 2048, 1342308425) [1021]:(1,0, 2048,
> 1342308425)  [1022]:(1,0, 1031, 1342308427) [1023]:(0,0, 0, 0)
>
> other desc in the ring is all zero。
>
> is there a bug?
>
> PS: it was normal with linux ixgbe driver。

  reply	other threads:[~2016-09-02  3:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 13:48 wei wang
2016-09-02  3:57 ` wei wang [this message]
2016-09-02 10:16   ` wei wang
2016-09-03  3:02     ` wei wang

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='CAPM6dUD6A95++Pb_wgVCmn11HsuqM7YYc08E=zU8kzS+RMZ1AA@mail.gmail.com' \
    --to=lnykww@gmail.com \
    --cc=dev@dpdk.org \
    --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).