From owner-freebsd-net@FreeBSD.ORG Sat Jul 1 07:54:04 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4DD616A417 for ; Sat, 1 Jul 2006 07:54:03 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1773843D53 for ; Sat, 1 Jul 2006 07:54:02 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so146673nzd for ; Sat, 01 Jul 2006 00:54:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pdhCddU7q6/w+EftU3LH4KVl88a5VOPB4Wx2rZ5hrHKgLPMXin+zMxe5ZEc3rktxOaRx2dKpcsGmBTnPzuEe3ZXtz6g3sKEYPvnZ7dJg4hbomt1751jod2LN37QEEdCIFmmcGhcUfeLLieqLhaKqgS8jRdlcgHPCInrNY/j/M/U= Received: by 10.36.36.4 with SMTP id j4mr44673nzj; Sat, 01 Jul 2006 00:54:02 -0700 (PDT) Received: by 10.36.12.11 with HTTP; Sat, 1 Jul 2006 00:54:01 -0700 (PDT) Message-ID: Date: Sat, 1 Jul 2006 02:54:01 -0500 From: "Nikolas Britton" To: pyunyh@gmail.com In-Reply-To: <20060701070245.GF54876@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060630060956.GA51353@cdnetworks.co.kr> <20060701051844.GE54876@cdnetworks.co.kr> <20060701070245.GF54876@cdnetworks.co.kr> Cc: freebsd-net@freebsd.org Subject: Re: Marvell YukonII Status Update? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jul 2006 07:54:04 -0000 On 7/1/06, Pyun YongHyeon wrote: > On Sat, Jul 01, 2006 at 01:33:51AM -0500, Nikolas Britton wrote: > > On 7/1/06, Pyun YongHyeon wrote: > > >On Fri, Jun 30, 2006 at 11:39:14PM -0500, Nikolas Britton wrote: > > > > On 6/30/06, Pyun YongHyeon wrote: > > > > >On Thu, Jun 29, 2006 at 10:53:52PM -0500, Nikolas Britton wrote: > > > > > > Anyone know what's going on with YukonII support in FreeBSD, > > > > > > specifically the Marvell chips used in PCI-Express add-on cards? > > > > > > > > > > > > Last I checked somebody was developing an experimental driver and > > > > > > Marvell had just released the code to their FreeBSD 5.x/6.x driver: > > > > > > mykbsd60x86-8.12.2.3.tar (bindary kmod package) > > > > > > mykbsd60x86-8.12.1.3-src.tgz (source code) > > > > > > > > > > > > > > > >I don't know current status of the driver. ATM FreeBSD YukonII > > > > >driver has stability issues and the driver needs big cleanups > > > > >if we import the driver into src tree. But I wouldn't do the > > > > >job and I'll spend my spare time to other thing. > > > > >I know, from my previous experience(sk(4), stge(4)), how > > > > >difficult to write a driver without a document and how hard to > > > > >write a correct driver without knowing hardware internals. I'm > > > > >sure there are many developers eager to write YukonII driver if > > > > >they can access the hardware documentation. However I think there > > > > >is no possibility that Marvell releases their chip documentations. > > > > > > > > > > > > > Marvell will give you the docs if you sign an NDA, I know it's stupid > > > > but I think it's the only way... unless we vote with the wallet... Who > > > > has PCI-Express gigabit NIC cards that meet the following criteria?: > > > > > > > > a) Supported by FreeBSD. > > > > b) Unencumbered documentation. > > > > c) Checksum offloading. > > > > > > > > > >There are many PCIe GigE hardwares upported by em(4) or bge/bce(4). > > >AFAIK the only hardware features not supported by em(4)/bge(4) driver > > >is TSO. And hardwares supported by em(4) also have a capability to > > >offload IPv6 checksumming too but it's not yet supported by the driver. > > > > > > > Will TCP Segmentation Offloading help if you already use a 9000 byte > > mtu, and is it going to be supported, someday, with em(4)/bge(4)?... > > I'm mostly clueless about TSO. > > > > Since not all hardwares support JUMBO frame and the maximum MTU > for the JUMBO frame varies among vendors/chipsets TSO would be > better suited for interoperability. > > I'm really want to see TSO support in our drivers. See the > following URL to see TSO effect in NetBSD wm(4) driver. > http://marc.theaimsgroup.com/?t=111662994600001&r=1&w=2 > I see... A poor mans jumbo frames, but only works with the sender, correct? If NetBSD supports it can't we more or less just copy and paste the code to FreeBSD? I know it's never that simple but... -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/