From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: daniel.lezcano@free.fr, ja@ssi.bg, eric.dumazet@gmail.com,
netdev@vger.kernel.org
Subject: Re: getsockopt(TCP_DEFER_ACCEPT) value change
Date: Tue, 05 Jan 2010 12:29:03 -0800 (PST) [thread overview]
Message-ID: <20100105.122903.241453878.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1001051526520.7024@wel-95.cs.helsinki.fi>
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Tue, 5 Jan 2010 15:40:57 +0200 (EET)
> In general, I wonder if there's something that mandates that a set/get
> pair of value should be equal?
There is no such requirement, we've been violating that premise since
day one for socket receive and send queue buffer limit socket options.
The kernel is always allowed to add fuzz or overhead adjustments to
whatever the user gives it. If the user wants to know what the kernel
actually ended up using, it get getsockopt() to find out.
prev parent reply other threads:[~2010-01-05 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 10:42 getsockopt(TCP_DEFER_ACCEPT) value change Daniel Lezcano
2010-01-05 13:40 ` Ilpo Järvinen
2010-01-05 14:11 ` Eric Dumazet
2010-01-05 14:45 ` Eric Dumazet
2010-01-05 15:45 ` Daniel Lezcano
2010-01-05 16:14 ` Eric Dumazet
2010-01-05 16:57 ` Daniel Lezcano
2010-01-05 20:29 ` David Miller [this message]
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=20100105.122903.241453878.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel.lezcano@free.fr \
--cc=eric.dumazet@gmail.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=ja@ssi.bg \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).