All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "İbrahim Ercan" <ibrahim.metu@gmail.com>
Cc: xdp-newbies@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	brouer@redhat.com
Subject: Re: ethtool isn't showing xdp statistics
Date: Wed, 12 Jun 2019 09:53:23 +0200	[thread overview]
Message-ID: <20190612095323.620c0791@carbon> (raw)
In-Reply-To: <CAK6Qs9kbWdRSer1LTz53BunJkvpQaa02YExen65Tha3HpGrW+w@mail.gmail.com>


On Wed, 12 Jun 2019 09:57:02 +0300 İbrahim Ercan <ibrahim.metu@gmail.com> wrote:

> I removed bridge and did same tests again. Unfortunately result is
> same :/

I sort of expected that, as the ethtool "rx_missed_errors" counter
says, that packets are dropped inside the NIC, before reaching Linux.
Something more fundamental is wrong with your setup.

You mentioned there was a switch between the machines in your lab.  One
possibility is that the switch is somehow corrupting the frames before
the reach the NIC, e.g. in these overload DDoS scenarios.  Try to
remove the switch from the equation (by directly connecting machine
back-to-back), to identify where the pitfall is...

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  reply	other threads:[~2019-06-12  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  9:55 ethtool isn't showing xdp statistics İbrahim Ercan
2019-06-10 10:15 ` Jesper Dangaard Brouer
2019-06-11  9:18   ` İbrahim Ercan
2019-06-11 10:42     ` Jesper Dangaard Brouer
2019-06-11 13:18       ` İbrahim Ercan
2019-06-11 14:45         ` Jesper Dangaard Brouer
2019-06-12  6:57           ` İbrahim Ercan
2019-06-12  7:53             ` Jesper Dangaard Brouer [this message]
2019-06-12  8:59               ` İbrahim Ercan
2019-06-13 13:02                 ` İbrahim Ercan

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=20190612095323.620c0791@carbon \
    --to=brouer@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=ibrahim.metu@gmail.com \
    --cc=xdp-newbies@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.