From: "Sebastião Santos Boavida Amaro" <sebastiao.amaro@tecnico.ulisboa.pt>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: xdp-newbies@vger.kernel.org
Subject: Re: XDP in virtual Ethernet devices
Date: Tue, 22 Jun 2021 16:35:59 +0100 [thread overview]
Message-ID: <00b3a957e3d1dc3a0b22ef62cd0eddd8@tecnico.ulisboa.pt> (raw)
In-Reply-To: <874kehd90a.fsf@toke.dk>
Thank you for the reply!
After experimenting more the problem is not related to docker
specifically but to the docker networks. When I run the same experiment
outside a docker network I am able to capture packets, however, when the
containers are deployed in a docker network I cannot capture packets.
Does anyone know why this might happen? Or was able to capture the
packets of docker containers inside networks?
Best Regards,
Sebastião Amaro
A 2021-06-01 14:12, Toke Høiland-Jørgensen escreveu:
> Sebastião Santos Boavida Amaro
> <sebastiao.amaro@tecnico.ulisboa.pt> writes:
>
>> Hello!
>> I am trying to use xdp_stats[1] (this program prints packets
>> passed/dropped) on the ethernet devices created by docker
>> containers(veth). I have iperf exchanging messages between containers
>> but xdp_stats does not capture any of the packets (XDP_PASS values do
>> not change) and CPU usage goes to 100%. It works fine on my laptop's
>> network device, but I have these issues with the docker network
>> devices
>> and I don't understand why.
>
> I don't think there's anything special about the veth devices Docker
> creates; so my immediate thought would be that this is due to
> differences in the kernel versions you're running on your laptop vs on
> docker. Some more details on this would be required to say anything
> more, though...
>
> -Toke
prev parent reply other threads:[~2021-06-22 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 14:52 XDP in virtual Ethernet devices Sebastião Santos Boavida Amaro
2021-06-01 13:12 ` Toke Høiland-Jørgensen
2021-06-22 15:35 ` Sebastião Santos Boavida Amaro [this message]
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=00b3a957e3d1dc3a0b22ef62cd0eddd8@tecnico.ulisboa.pt \
--to=sebastiao.amaro@tecnico.ulisboa.pt \
--cc=toke@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).