From: David Ashley <dash@xdr.com>
To: val@nmt.edu
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: BUG: udp socket, getsockopt + setsockopt
Date: Tue, 29 Jan 2002 19:26:56 -0800 [thread overview]
Message-ID: <200201300326.g0U3Qu600178@dave.home> (raw)
I forgot to mention it doesn't act the same on my x86 desktop running
linux. I don't recall what version. On my pc there is no trouble.
Oh well.
Thanks--
Dave
>When you set SO_RCVBUF with setsockopt, the kernel allocates twice the
>memory you set. This has something to do with BSD compatibility and
>storing internal kernel structures in the memory allocated for the
>recv buf. Try getsockopt after you setsockopt.
>
>This is ostensibly a feature, not a bug. Search the linux-kernel
>archives for "so_rcvbuf" and "David Miller". Hint: you probably won't
>convince Dave to change his mind.
>
>-VAL
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-01-30 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 3:26 David Ashley [this message]
2002-01-30 3:41 ` BUG: udp socket, getsockopt + setsockopt Val Henson
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 3:22 David Ashley
2002-01-29 16:49 David Ashley
2002-01-29 16:58 ` Josh Horvath
2002-01-30 0:05 ` Val Henson
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=200201300326.g0U3Qu600178@dave.home \
--to=dash@xdr.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=val@nmt.edu \
/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).