From: Dave Taht <dave@taht.net>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] extending SO_SNDLOWAT and SO_RCVLOWAT to udp?
Date: Thu, 06 Apr 2017 07:55:07 -0700 [thread overview]
Message-ID: <87bms9oab8.fsf@nemesis.taht.net> (raw)
I recently hit a several circumstances where it would have been nice to
have SO_SNDLOWAT and SO_RCVLOWAT options working for udp (and netlink)
sockets.
In poking about the kernel it looks like these are implemented for TCP
only. (?) I'm curious if anyone has tried to extend them to more socket
types? It seems like it would be useful to have for things like QUIC in
particular. NFS?
I hit it 3 different ways:
* select was returning a socket writable (because it had a byte
available), but then EAGAIN when I tried to write a full size
packet, so I went back to the select, which returned immediately
so I went back to the EAGAIN....
* I completely flooded a multicast queue (11 minutes worth) - while
that issue was in the driver, after I fix that, having some means
of further backpressure up the stack would be good.
* I actually wanted to have recvmmsg block til it had a few
packets in it.
reply other threads:[~2017-04-06 14:55 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
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=87bms9oab8.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=bloat@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