From: Andi Kleen <ak@suse.de>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>
Cc: "Stuart MacDonald" <stuartm@connecttech.com>,
linux-kernel@vger.kernel.org
Subject: Re: TCP stack behaviour question
Date: Wed, 20 Sep 2006 11:55:58 +0200 [thread overview]
Message-ID: <200609201155.58197.ak@suse.de> (raw)
In-Reply-To: <20060919145024.46580@gmx.net>
> Interestingly, at this point in the man pages source there
> is the following commented out text:
Yes that was me. On second thought I suppose I was right back then that this
feature is too dubious to be documented. So better keep it
undocumented and drop the change.
-Andi
>
> .\" FIXME . Is it a good idea to document that? It is a dubious feature.
> .\" On
> .\" .B SOCK_STREAM
> .\" sockets,
> .\" .I IP_RECVERR
> .\" has slightly different semantics. Instead of
> .\" saving the errors for the next timeout, it passes all incoming
> .\" errors immediately to the user.
> .\" This might be useful for very short-lived TCP connections which
> .\" need fast error handling. Use this option with care:
> .\" it makes TCP unreliable
> .\" by not allowing it to recover properly from routing
> .\" shifts and other normal
> .\" conditions and breaks the protocol specification.
>
> Cheers,
>
> Michael
next prev parent reply other threads:[~2006-09-20 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 17:28 TCP stack behaviour question Stuart MacDonald
2006-09-18 8:29 ` Andi Kleen
2006-09-18 13:20 ` Stuart MacDonald
2006-09-18 13:54 ` Andi Kleen
2006-09-18 14:19 ` Stuart MacDonald
2006-09-18 14:31 ` Andi Kleen
2006-09-18 15:38 ` Michael Kerrisk
2006-09-18 17:01 ` Stuart MacDonald
2006-09-19 6:13 ` Michael Kerrisk
2006-09-19 6:47 ` Andi Kleen
2006-09-19 14:50 ` Michael Kerrisk
2006-09-20 9:55 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-18 18:29 Stuart MacDonald
2006-09-19 12:03 ` Samuel Tardieu
2006-09-19 14:00 ` Stuart MacDonald
2006-09-20 9:54 ` Andi Kleen
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=200609201155.58197.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=stuartm@connecttech.com \
/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