DPDK patches and discussions
 help / color / mirror / Atom feed
From: 최익성 <pnk003@naver.com>
To: dev@dpdk.org
Subject: [dpdk-dev]  When I run test-pmd, most of received packets(loop-backed packet) have RX-error.
Date: Tue, 20 Oct 2015 15:12:51 +0900 (KST)	[thread overview]
Message-ID: <a362825a655e253a67291c5afd42b0@cweb01.nm.nhnsystem.com> (raw)

Dear DPDK experts.
 
Thank you very much for your best great efforts and precious answers.
 
 
When I run test-pmd, most of received packets are RX-error.
 
The computer has two 10GbE ports Intel NIC and the two ports are loop-backed each other.
 
The result shows that the loop-backed packets have rx-error occured from ethernet device port.
 
The rx-error ( ierrors) seems to be counted by rte_eth_stats_get(uint8_t port_id, struct rte_eth_stats *stats) function in ~/dpdk/lib/librte_ether/rte_ethdev.c
 
Then this rte_eth_stats_get() function calls (*dev-&gt;dev_ops-&gt;stats_get)(dev, stats);
 
However, I can't find and trace the function (*dev-&gt;dev_ops-&gt;stats_get)().
 
Would you tell me how can I find the function?
 
Would you tell me why this receive errors occurs for what reasons?
 
 
I tested it in two xeon computers with different OS.
 
   Fedora 22 (linux kernel version 4.2.3-200.fc22.x86_64, DPDK 2.1.0).
   Ubuntu 14.04.1 LTS(linux kernel version : 3.13.0-34-generic, DPDK 2.1.0).  
 
Both experiments show the same result with rx-errors.
 
I will really appreciate if I can be given any advice and answers.
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.


             reply	other threads:[~2015-10-20  6:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  6:12 최익성 [this message]
2015-10-20 13:50 ` Kyle Larose
2015-10-21  2:04   ` 최익성
2015-10-21  2:07     ` Choi, Sy Jong
2015-10-21  2:10       ` 최익성
2015-10-21 13:30       ` 최익성

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=a362825a655e253a67291c5afd42b0@cweb01.nm.nhnsystem.com \
    --to=pnk003@naver.com \
    --cc=dev@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).