[From nobody Wed Feb 21 23:40:14 2007 Return-path: <netrek@gmail.com> X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on dors.lan X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.7 Envelope-to: james@localhost Delivery-date: Thu, 22 Feb 2007 16:39:27 +1100 Received: from localhost ([127.0.0.1] helo=dors.lan ident=james) by dors.lan with esmtp (Exim 4.63) (envelope-from <netrek@gmail.com>) id 1HK6fv-0001UO-EF for james@localhost; Thu, 22 Feb 2007 16:39:27 +1100 Received: from popmail.real-time.com by dors.lan with POP3 (fetchmail-6.3.6) for <james@localhost> (single-drop); Thu, 22 Feb 2007 16:39:27 +1100 (EST) Received: from smtpgrey-1.real-time.com (smtpgrey-1.real-time.com [208.20.202.5]) by enchanter.real-time.com (8.12.10/8.12.10) with ESMTP id l1M5L7bu011781 for <quozl@real-time.com>; Wed, 21 Feb 2007 23:21:07 -0600 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from shadowknight.real-time.com (shadowknight.real-time.com [208.20.202.14]) by smtpgrey-1.real-time.com (Postfix) with ESMTP id CC4971867E0 for <quozl@real-time.com>; Wed, 21 Feb 2007 23:21:00 -0600 (CST) Received: from smtpgrey-2.real-time.com ([208.20.203.5]) by shadowknight.real-time.com with esmtp (Exim 4.63 #1 ) id 1HK6Ny-000409-QG for <quozl@us.netrek.org>; Wed, 21 Feb 2007 23:20:57 -0600 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by smtpgrey-2.real-time.com (Postfix) with ESMTP id 75B70B42F for <quozl@us.netrek.org>; Wed, 21 Feb 2007 23:20:46 -0600 (CST) Received: by nf-out-0910.google.com with SMTP id a27so437054nfc for <quozl@us.netrek.org>; Wed, 21 Feb 2007 21:20:45 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GiAX7DaihWtP+KyaHwdV33iwcPHWYPY+zDQ+eAx3a2QjHT+bqO5kR+5BUK4QLDWEDvItHNbC6G2MMInFbtJhdYtjCaZxThqKrm9ifZ13Dl8g+bVt0n/T8VfXurdjm/GLs4Nh1jc2ZhDP/5TXEJzyUAEa7ojE7mXhABzC4v/K27o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=RAoJNCAb2Q9j8D1L1jovxGu2HC80J47OTW1PVBbcGGRFriqWy0fQNCo3m7tkpET2wBxsGBZLDqQIDsZfAVQG7bsVikLCDno+y3/g9XE6K3Yx8vOWeHyeEbyJe0LiKBi70G6oOa7lgtpnopmMpEkbjGZ4M9rF8ZX7fqET81wqifc= Received: by 10.82.148.7 with SMTP id v7mr46569bud.1172121644493; Wed, 21 Feb 2007 21:20:44 -0800 (PST) Received: by 10.82.188.9 with HTTP; Wed, 21 Feb 2007 21:20:44 -0800 (PST) Message-ID: <ecfa260c0702212120q1e89dc61pf88132f985f852de@mail.gmail.com> Date: Thu, 22 Feb 2007 00:20:44 -0500 From: Zach <netrek@gmail.com> To: "James Cameron" <quozl@us.netrek.org> Subject: TCP_NODELAY MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline http://archives.real-time.com/vanilla-list/1999/May/msg00046.html Has this been fixed in the server? Is there a way I can tell Linux kernel to NOT use the Nagle routing algorithm which causes TCP packet amalgamation when I am using TCP packets or would this break other things in Linux? Zach ]