From owner-freebsd-net Fri Sep 27 10:43:42 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 3EF6E37B401 for ; Fri, 27 Sep 2002 10:43:41 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BFCB43E42 for ; Fri, 27 Sep 2002 10:43:40 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.5) with ESMTP id g8RHhdVo011910 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 27 Sep 2002 13:43:40 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.5/Submit) id g8RHhbu6011907; Fri, 27 Sep 2002 13:43:37 -0400 (EDT) (envelope-from wollman) Date: Fri, 27 Sep 2002 13:43:37 -0400 (EDT) From: Garrett Wollman Message-Id: <200209271743.g8RHhbu6011907@khavrinen.lcs.mit.edu> To: "Petri Helenius" Cc: Subject: SO_TIMESTAMP In-Reply-To: <09ce01c26630$ba177cc0$8c2a40c1@PHE> References: <09ce01c26630$ba177cc0$8c2a40c1@PHE> 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 < said: > 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? 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. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message