From: Christian Seiler <[email protected]> Date: Tue, 3 Mar 2015 01:32:54 +0100
> Rationale: applications may want to control how many datagrams the > kernel buffers before senders are blocked. A prominent example would be > to create a socket for syslog early at boot but only consume messages > once enough of the system has been set up. The default queue length of > 11 messages (= 10 + 1) is too low for this kind of application. I never like arguments that talk about forcing the kernel to do excessive buffering for an application. Queue this stuff in the userspace side, then you can have as many messages backlogged as you like _without_ consuming unswappable kernel memory. I'm tossing this, you're going to have to do a much better job explaining to me why userspace cannot take upon itself the burdon of queueing data until it can be sent. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
