Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932203AbXJQWAb (ORCPT ); Wed, 17 Oct 2007 18:00:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754696AbXJQWAW (ORCPT ); Wed, 17 Oct 2007 18:00:22 -0400 Received: from ioctl.codeblau.de ([80.190.240.67]:57704 "EHLO codeblau.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754614AbXJQWAW (ORCPT ); Wed, 17 Oct 2007 18:00:22 -0400 Date: Thu, 18 Oct 2007 00:00:19 +0200 From: Felix von Leitner To: Chuck Ebbert Cc: linux-kernel@vger.kernel.org, Netdev Subject: Re: bizarre network timing problem Message-ID: <20071017220019.GA22765@codeblau.de> References: <20071017205127.GA21334@codeblau.de> <47167BDE.4000103@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47167BDE.4000103@redhat.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 686 Lines: 18 Thus spake Chuck Ebbert (cebbert@redhat.com): > > Any ideas what could cause this? > (cc: netdev) Maybe I should mention this, too: accept(5, {sa_family=AF_INET6, sin6_port=htons(59821), inet_pton(AF_INET6, "::ffff:127.0.0.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [18446744069414584348]) = 8 setsockopt(8, SOL_TCP, TCP_NODELAY, [1], 4) = 0 And if it would be the Nagle algorithm, it should also impact the ethernet case. Felix - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/