From: Martin Clausen <martin@ostenfeld.dk>
To: linux-kernel@vger.kernel.org
Subject: Maximum socket buffer sizes
Date: Sat, 30 Jun 2001 15:39:12 +0200 [thread overview]
Message-ID: <20010630153912.C1352@ostenfeld.dk> (raw)
Hi!
What are the maximum socket buffer sizes for:
net.core.rmem.*
net.core.wmem.*
net.core.optmem_max
As far as i can tell these are ones to adjust when "tuning"
e.g. the netlink sockets between the kernel and userspace?
I have not been able to find this information anywhere...
Best regards
Martin
--
Failure is not an option. It comes bundled with your Microsoft product.
reply other threads:[~2001-06-30 13:36 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=20010630153912.C1352@ostenfeld.dk \
--to=martin@ostenfeld.dk \
--cc=linux-kernel@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).