Thread (1 message) 1 message, 1 author, 2002-01-30

Re: BUG: udp socket, getsockopt + setsockopt

From: Val Henson <hidden>
Date: 2002-01-30 03:41:02

I'm not sure what version this change appeared.  Also, your pc may
have different default socket size settings.  This command will show
you both the max and default settings:

cat /proc/sys/net/core/?mem_*

(You can also set them in the usual way.)

-VAL

On Tue, Jan 29, 2002 at 07:26:56PM -0800, David Ashley wrote:
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
quoted
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/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help