From: David Miller <davem@davemloft.net>
To: christian@iwakd.de
Cc: netdev@vger.kernel.org, dan@mindstab.net, edumazet@google.com,
hannes@stressinduktion.org, linux-api@vger.kernel.org
Subject: Re: [PATCH] net: add SO_MAX_DGRAM_QLEN for AF_UNIX SOCK_DGRAM sockets
Date: Mon, 02 Mar 2015 21:38:07 -0500 (EST) [thread overview]
Message-ID: <20150302.213807.367185406305242762.davem@davemloft.net> (raw)
In-Reply-To: <1425342774-32667-1-git-send-email-christian@iwakd.de>
From: Christian Seiler <christian@iwakd.de>
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.
next prev parent reply other threads:[~2015-03-03 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 0:32 [PATCH] net: add SO_MAX_DGRAM_QLEN for AF_UNIX SOCK_DGRAM sockets Christian Seiler
2015-03-03 2:38 ` David Miller [this message]
2015-03-03 9:04 ` Christian Seiler
[not found] ` <0b5908020d83bcbaa7f4938e5cb433ea-+GPkE3DhqnY@public.gmane.org>
2015-03-03 14:30 ` Eric Dumazet
2015-03-03 15:05 ` Christian Seiler
[not found] ` <55ee39bff7875967acb06f25fa695f95-+GPkE3DhqnY@public.gmane.org>
2015-03-03 15:56 ` Eric Dumazet
2015-03-03 18:59 ` David Miller
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=20150302.213807.367185406305242762.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christian@iwakd.de \
--cc=dan@mindstab.net \
--cc=edumazet@google.com \
--cc=hannes@stressinduktion.org \
--cc=linux-api@vger.kernel.org \
--cc=netdev@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 NNTP newsgroup(s).