public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raphael_Manfredi@pobox.com (Raphael Manfredi)
To: linux-kernel@vger.kernel.org
Subject: Re: setsockopt(SOL_SOCKET, SO_SNDBUF) broken on 2.4.18?
Date: 25 Feb 2002 22:19:42 GMT	[thread overview]
Message-ID: <a5ed9u$3tp$1@lyon.ram.loc> (raw)
In-Reply-To: <2871.1014671286@nice.ram.loc> <Pine.LNX.3.95.1020225163035.29043C-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1020225163035.29043C-100000@chaos.analogic.com>

Quoting root@chaos.analogic.com from ml.linux.kernel:
:This came up a few months ago. Don't halve the size. The value was
:explained to NOT be a bug even though it doesn't make sense to us
:mortals. Just set the buffer size without reading anything. It will
:be fine. The explaination was somewhat smokey, but It seems as though
:two buffers are set aside or something like that. Just don't read
:the size. Set it and forget it.

The problem is that I don't want to shrink the buffer size, hence I need
to read the current size.  Do I need to halve the returned value from
getsockopt() then?

Raphael

  reply	other threads:[~2002-02-25 22:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 21:08 setsockopt(SOL_SOCKET, SO_SNDBUF) broken on 2.4.18? Raphael Manfredi
2002-02-25 21:34 ` Richard B. Johnson
2002-02-25 22:19   ` Raphael Manfredi [this message]
2002-02-25 23:21     ` Alan Cox
2002-02-25 22:39 ` Alan Cox
2002-02-26  7:46   ` Raphael Manfredi
2002-02-26  9:39     ` Alan Cox
2002-02-26 12:54       ` Raphael Manfredi
2002-02-27 16:17     ` Horst von Brand
     [not found] <E16_Tly-0006Va-00@the-village.bc.nu>
2002-02-26  0:11 ` Ton Hospel

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='a5ed9u$3tp$1@lyon.ram.loc' \
    --to=raphael_manfredi@pobox.com \
    --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