From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Xdp <xdp-newbies@vger.kernel.org>
Cc: brouer@redhat.com
Subject: BPF related blogpost on network troubleshooting at Facebook
Date: Fri, 29 Apr 2022 17:13:02 +0200 [thread overview]
Message-ID: <e60747ef-e748-dcd7-7e3e-77b4ebc8b22d@redhat.com> (raw)
Hi BPF-fans,
Super awesome BPF related blogpost[0] by Jakub "Kuba" Kicinski (one of
the netdev kernel maintainers).
- [0]
https://developers.facebook.com/blog/post/2022/04/25/investigating-tcp-self-throttling-triggered-overload/
On how Facebook used BPF to troubleshoot a productions issue with TCP
bufferbloat at high data-center rates, that caused CPUs to spin 100% in
netstack NAPI processing stage.
I also loved their approach to implement CoDel in XDP for throttling the
RX-queue (that were overflowing) at an earlier stage that netstack as
the CPU was in a 100% overload state. They didn't share their CoDel BPF
implementation, but I've added a link here[3] to my own code.
--Jesper
Social media links:
[1] https://twitter.com/JesperBrouer/status/1520051491733712896
[2]
https://www.linkedin.com/feed/update/urn:li:activity:6925818081055289344/
[3]
https://github.com/xdp-project/bpf-examples/blob/master/traffic-pacing-edt/codel_impl.h
reply other threads:[~2022-04-29 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e60747ef-e748-dcd7-7e3e-77b4ebc8b22d@redhat.com \
--to=jbrouer@redhat.com \
--cc=brouer@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).