Date: Wed, 21 Feb 2007 16:39:06 +0100 From: Andre Oppermann <andre@freebsd.org> To: Andre Guibert de Bruet <andy@siliconlandmark.com> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, current@freebsd.org Subject: Re: excessive TCP duplicate acks? Message-ID: <45DC679A.9030304@freebsd.org> In-Reply-To: <DF12957F-D92B-495A-A815-2F5ECFD83852@siliconlandmark.com> References: <17850.13146.266196.499166@grasshopper.cs.duke.edu> <2FE2BC67-A829-4BF9-B606-65DE1393E8DE@siliconlandmark.com> <17883.19584.99616.808623@grasshopper.cs.duke.edu> <DF12957F-D92B-495A-A815-2F5ECFD83852@siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Andre Guibert de Bruet wrote: > On Feb 20, 2007, at 2:31 PM, Andrew Gallatin wrote: > >> Thanks for reporting this. I'm glad I'm not the only one who is >> seeing this! > > > I discovered this while testing out a new multi-homed bonded-T1 > installation. I was wondering why I was getting no more than ~170KB/ s. > So far, here are the data points that I have gathered: > > - It affects more than one type of NIC (em0). > - It happens regardless of hardware checksum enabled status. > - It happens independent of IP aliasing. > - I tested GENERIC as of Feb 19 and it is affected. > - A kernel from December 15th, 2006 exhibits this problem. > - The affected system is connected to a Linksys 24-port unmanaged > gigabit switch (I have the exact same hardware working just fine with > 5.5-STABLE on the same switch). Today I finally got some spare time and tried to track this down. However there is no obvious smoking gun to be seen. I'll dig further. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45DC679A.9030304>