General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Bloat] talking at linux plumbers in portugal next week
Date: Mon, 2 Sep 2019 17:47:02 -0700	[thread overview]
Message-ID: <CAA93jw5OS9zxQasFFn6C2354yvyFO0xin+O6jYFrx46Ax5Tx=g@mail.gmail.com> (raw)

I'm doing a talk on my ipv4 unicast extensions project next week. Toke
and jesper and stephen hemminger are there, anyone else?

There's also some "bloat" business of course to do. Obviously talk
about the state of the bloat, the l4s & sce work, etc.

but: I have a bunch of other "plumbing" stuff that's been bugging me
lately, and perhaps there are those here that might have
more? I should try to find people to talk to about, or knew who I should?

1) Recently (in a limited set of coffee shop tests), I saw 30+% of
ipv4 tcp syns being retried. That's scary, I don't know if anyone's
tracking that in any way? It seems possible to track it with
in-browser statistics, possibly. I'm afraid a syn-limiter is in place
with copy-pasted parameters set in the 90s - openwrt's default, last I
looked, was 25/sec.
2) I'd really like somehow for atomic route updates to "just work". I
think it's working now for ipv4, at least, as I saw a commit go
in for it for bird, recently. That plus sorta-kinda-wanting to see
pmtu work better for udp is on my mind.
3) Our biggest problem bufferbloat-wise is inbound shaping and I don't
know how to make it better aside from resuming work on a smarter
policer.
4)?

I'm pretty broke as usual (LF is paying for the plane and airbnb (thx
LF!), but not food or my time), if anyone could throw a few bucks into
my gofundme or patreon, it would be appreciated.

--

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

             reply	other threads:[~2019-09-03  0:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  0:47 Dave Taht [this message]
2019-09-03 12:23 ` Mikael Abrahamsson
2019-09-03 14:21   ` Dave Taht
2019-09-03 14:35     ` [Bloat] Revising the synflood limit Dave Taht
2019-09-10 18:08       ` [Bloat] [Cerowrt-devel] " Maciej Sołtysiak
2019-09-10 22:35         ` Dave Taht
2019-09-23  9:37           ` Maciej Sołtysiak
2019-09-03 14:45     ` [Bloat] talking at linux plumbers in portugal next week Toke Høiland-Jørgensen
2019-09-03 14:47       ` Dave Taht
2019-09-03 15:10         ` Toke Høiland-Jørgensen
2019-09-03 15:21           ` Dave Taht
2019-09-03 15:22     ` [Bloat] [Cerowrt-devel] " Sebastian Moeller

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5OS9zxQasFFn6C2354yvyFO0xin+O6jYFrx46Ax5Tx=g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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