From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932398AbWGRUvQ@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932398AbWGRUvQ (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 18 Jul 2006 16:51:16 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932397AbWGRUvP
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 18 Jul 2006 16:51:15 -0400
Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:14239
	"EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP
	id S932398AbWGRUvP (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 18 Jul 2006 16:51:15 -0400
Date: Tue, 18 Jul 2006 13:51:38 -0700 (PDT)
Message-Id: <20060718.135138.94559559.davem@davemloft.net>
To: oumer@kom.aau.dk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange TCP SACK behaviour in Linux TCP
From: David Miller <davem@davemloft.net>
In-Reply-To: <44BD0A5F.4090001@kom.aau.dk>
References: <44BD0A5F.4090001@kom.aau.dk>
X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


Please ask networking questions on the networking developer
list, netdev@vger.kernel.org

You are surely to get more relevant eyeballs on your problem
there.