From owner-freebsd-hackers Thu Sep 27 8:58:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E94837B42C for ; Thu, 27 Sep 2001 08:58:11 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA13398; Thu, 27 Sep 2001 11:57:30 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f8RFv4o83861; Thu, 27 Sep 2001 11:57:04 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15283.19536.410864.339942@grasshopper.cs.duke.edu> Date: Thu, 27 Sep 2001 11:57:04 -0400 (EDT) To: Ronald G Minnich Cc: Andrew Gallatin , "Louis A. Mamakos" , Subject: Re: TCP&IP cksum offload on FreeBSD 4.2 In-Reply-To: References: <15283.14648.430630.163513@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ronald G Minnich writes: > > you still have a potential problem here with variance in chipsets, namely > the case of broken ABORT or other unusual PCI cycle handling (missed word > problem). I agree it's a low probability. But we've seen it, just a week > or two ago on a brand new box. > > But then we tend to see things here nobody else sees due to our scale. > > ron At this level, you're basically screwed. A sofware checksum isn't even an option on other PCI users, like disk controllers. If you don't trust your PCI chipset, what do you do about things like that? I'm rather curious -- what was the problematic hardware combination? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message