From: Christian Schmid <webmaster@rapidforum.com>
To: netdev@oss.sgi.com
Subject: How to remove TCP-limits?
Date: Sat, 29 Jan 2005 17:06:53 +0100 [thread overview]
Message-ID: <41FBB49D.2020809@rapidforum.com> (raw)
Referring to the following:
>In 2.6.10 there has been a "bug" introduced. You may also call it a feature, but its a crappy
>feature for big servers. It seems the kernel is dynamically adjusting the buffer-space available
>for sockets. Even if send-buffer has been set to 1024 KB, the kernel blocks at less if there are
>enough sockets in use. If you have 10 sockets with 1024 KB each, they do not block at all, using
>full 1024 KB. If you have 4000 sockets, they only use 200 KB. So it seems its blocking at 800 MB.
>This is good, if you have a 1/3 system, because else the kernel would run out of low mem. But I
>have a 2/2 system and I need them for buffers. So what can I do? Where can I adjust the "pool"?
How can I disable this? I have been searching the code but I can't find it. Or can I at least adjust
it somehow? Thank you in advance.
Best regards,
Christian Schmid - RapidTec
reply other threads:[~2005-01-29 16:06 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=41FBB49D.2020809@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.