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>
Subject: Re: ethtool isn't showing xdp statistics
Date: Tue, 11 Jun 2019 16:45:25 +0200 [thread overview]
Message-ID: <20190611164525.6f8e845c@carbon> (raw)
In-Reply-To: <CAK6Qs9mncU4E-ZBSb8RNZrGqUyruU4of-fStr9vhLVmCVHg+TA@mail.gmail.com>
On Tue, 11 Jun 2019 16:18:17 +0300
İbrahim Ercan <ibrahim.metu@gmail.com> wrote:
> and loaded with
> ./ip -force link set dev enp7s0f0 xdp object dropudp.o sec prog
>
> I also realized that after loading xdp code, network go down about 5
> second, Is that normal?
>
> I'm using bridged topology. I don't know it is important or not.
>
> # brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.00900b3b696c yes enp7s0f0 enp7s0f1
I would recommend removing the bridge setup, for isolation the issue,
as this could be the issue. XDP doesn't cooperate with the bridge
code, and it works on a layer before the bridge.
For the ixgbe driver it does a full link down/up (to reconfigure all
the NIC queues), which is why you likely you see this 5 sec issue, as
you have enabled STP on your bridge. (Note, replacing an XDP-prog with
another XDP-prog does not require this link down/up).
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2019-06-11 14:45 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 [this message]
2019-06-12 6:57 ` İbrahim Ercan
2019-06-12 7:53 ` Jesper Dangaard Brouer
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=20190611164525.6f8e845c@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.