From: Philippe Troin <phil@fifi.org>
To: Kalpesh Shah <kalpesh@cs.utexas.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Socket options
Date: 16 Aug 2001 19:11:13 -0700 [thread overview]
Message-ID: <874rr7zb9a.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0108162055050.24575-100000@cabaco.cs.utexas.edu>
In-Reply-To: <Pine.GSO.4.33.0108162055050.24575-100000@cabaco.cs.utexas.edu>
Kalpesh Shah <kalpesh@cs.utexas.edu> writes:
> I would like to be CC'ed any answers/comments to my question.
>
> are /proc/sys/net/ipv4/tcp_rmem and /proc/sys/net/ipv4/tcp_wmem the socket
> Buffer (receive and send respectively) Sizes in the linux kernel.
>
> If yes then how come when I try to set these buffer sizes by using the
> SO_RCVBUFF and SO_SNDBUFF variables it automatically multiplies the values
> by 2 ????
To remain BSD-compatible.
There was a thread about this on lkml one week ago. Check the
archives.
next prev parent reply other threads:[~2001-08-17 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 2:01 Kalpesh Shah
2001-08-17 2:11 ` Philippe Troin [this message]
2001-08-17 2:15 ` Kalpesh Shah
2001-08-17 2:40 ` David Schwartz
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=874rr7zb9a.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=kalpesh@cs.utexas.edu \
--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
all inboxes | Powered by JetHome®