public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Andi Kleen'" <ak@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: TCP stack behaviour question
Date: Mon, 18 Sep 2006 10:19:08 -0400	[thread overview]
Message-ID: <002801c6db2d$67d8a3a0$294b82ce@stuartm> (raw)
In-Reply-To: <200609181554.15820.ak@suse.de>

From: Andi Kleen [mailto:ak@suse.de] 
> > # man 7 ip
> > ..
> >                Note that TCP has no error queue; MSG_ERRQUEUE is
> > illegal on SOCK_STREAM sockets.  Thus all errors are returned by
> > socket function return or SO_ERROR only.
> > 
> > Maybe the man page is wrong? That's from my FC 3 install.
> 
> The sentence is correct, but TCP has a IP_RECVERR that works
> differently without a queue. Basically it doesn't delay the error 
> reporting for incoming ICMPs to the last retransmit, but reports
> them immediately. This is documented in tcp(7)

I read that too, but didn't know which one was correct, so I erred on
the side of caution and believed ip(7).

Good to know, I'll look into that. Thanks.

..Stu


  reply	other threads:[~2006-09-18 14:19 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 [this message]
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
  -- 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='002801c6db2d$67d8a3a0$294b82ce@stuartm' \
    --to=stuartm@connecttech.com \
    --cc=ak@suse.de \
    --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