From owner-freebsd-net@FreeBSD.ORG Sat Jul 1 07:00:17 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 BF3D516A40F for ; Sat, 1 Jul 2006 07:00:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E84F543D49 for ; Sat, 1 Jul 2006 07:00:16 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so142729nzd for ; Sat, 01 Jul 2006 00:00:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=DSbt7Dijvvu4zbRmmf2ygN5hir80O9pfMsdE1gub3WZJM0qjFTMMpyp/6uxk1rGWGHYzO/D7hZtjjLPlKuh/Mqt5RDB91YUwtSkrVHUBWMY/yrKPfJ73FSInoyKyNVKzmoKlJEosOClPn5D7axoiy9l/SMbLmPBIPOAOMh8Qkj8= Received: by 10.36.159.15 with SMTP id h15mr15626nze; Sat, 01 Jul 2006 00:00:16 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 14sm4508569nzp.2006.07.01.00.00.12; Sat, 01 Jul 2006 00:00:15 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k6172kDF056540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Jul 2006 16:02:46 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k6172jMC056539; Sat, 1 Jul 2006 16:02:45 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 1 Jul 2006 16:02:45 +0900 From: Pyun YongHyeon To: Nikolas Britton Message-ID: <20060701070245.GF54876@cdnetworks.co.kr> References: <20060630060956.GA51353@cdnetworks.co.kr> <20060701051844.GE54876@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i 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 Reply-To: pyunyh@gmail.com 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:00:17 -0000 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 -- Regards, Pyun YongHyeon