From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 22:36:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C5E916A4CE for ; Wed, 3 Nov 2004 22:36:46 +0000 (GMT) Received: from mail.trippynames.com (mail.trippynames.com [38.113.223.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F6843D41 for ; Wed, 3 Nov 2004 22:36:46 +0000 (GMT) (envelope-from sean@chittenden.org) Received: from localhost (localhost [127.0.0.1]) by mail.trippynames.com (Postfix) with ESMTP id 49FCBA9439 for ; Wed, 3 Nov 2004 14:36:45 -0800 (PST) Received: from mail.trippynames.com ([127.0.0.1]) by localhost (rand.nxad.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 94036-03 for ; Wed, 3 Nov 2004 14:36:43 -0800 (PST) Received: from [192.168.123.123] (unknown [38.113.223.82]) by mail.trippynames.com (Postfix) with ESMTP id 3BA64A8C50 for ; Wed, 3 Nov 2004 14:36:43 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: References: <34cb7c840411030155710d8a26@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sean Chittenden Date: Wed, 3 Nov 2004 14:36:40 -0800 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Status of the sk driver/NIC (was: Re: if_sk patch to get more info from people with problems) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 22:36:46 -0000 > I was talking about your small patch. FreeBSD 5.3RC2-amd64 was working > fine for some 18 h even with SMP compiled kernel until I have tried > file copying over NFS (using linux 2.6.9 as NFS client). Performance > was poor and after incomplite copy of single file system rebooted with > panic. It was also strange that copying of 700mb took some 30 min. > on 100Mbit/s FD. After that I have applied small two lines patch, > recompiled kernel and although I have coppied something like 100Gb of > different mp3 and avi files over NFS - so far everything seems ok. I > haven't compiled kernel with options WITNESS but it was my intention > and will do so if I experience any further (if any) sk driver caused > suspected crashes. Can someone authoritatively give me a quick answer regarding this? *) Is the sk driver not working/not working properly? *) Is the sk driver making up for deficiencies in the hardware? *) Will the sk driver be able to make up for the deficiencies in the hardware such that sk will perform well enough for most uses (under no pretenses that it will perform as well as an em nic/driver)? Sorry, I've been following this for a while. I have a few machines with an sk on the famous K8V SE Deluxe, but am exclusively using em0 instead of sk0. At some point I'd like to turn up the sk0 NIC and use OSPF to multipath traffic... but that's all predicated on the sk0 not sucking too much (sk can be slow, just can't cause the machine to crash). -sc -- Sean Chittenden