From owner-freebsd-net Fri Sep 27 11:38:59 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A63537B401 for ; Fri, 27 Sep 2002 11:38:58 -0700 (PDT) Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA6743E42 for ; Fri, 27 Sep 2002 11:38:55 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from PHE (silver.he.iki.fi [193.64.42.241]) by silver.he.iki.fi (8.12.6/8.11.4) with SMTP id g8RIcSUW047589; Fri, 27 Sep 2002 21:38:50 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <0a2301c26655$22c4eea0$8c2a40c1@PHE> From: "Petri Helenius" To: "Garrett Wollman" Cc: References: <09ce01c26630$ba177cc0$8c2a40c1@PHE> <200209271743.g8RHhbu6011907@khavrinen.lcs.mit.edu> Subject: Re: SO_TIMESTAMP Date: Fri, 27 Sep 2002 21:38:39 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > Is there a reason why SO_TIMESTAMP does not work with TCP sockets > > but only with RAW and UDP ? > > Because it doesn't really make sense? But it would. It would let me know how long it took the process to get to the data I´m currently reading from the socket. (and notify operator to buy more hardware if it took too long) > > Since the TCP stream may be arbitrarily re-ordered, knowing when a > packet arrived is not particularly useful to an application. If you > really care, you should probably use BPF instead. > Are you suggesting to reimplement TCP sockets in userland? Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message