Date: Mon, 03 Jul 2006 12:49:38 +0200 From: Christian Brueffer <brueffer@FreeBSD.org> To: Pyun YongHyeon <pyunyh@gmail.com> Cc: freebsd-net@freebsd.org, Nikolas Britton <nikolas.britton@gmail.com> Subject: Re: Marvell YukonII Status Update? Message-ID: <20060703104938.GA4468@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <20060703082104.GB64457@cdnetworks.co.kr> References: <ef10de9a0606292053i31abe4e2na30ec0028b54da8e@mail.gmail.com> <20060630060956.GA51353@cdnetworks.co.kr> <ef10de9a0606302139t71acf183w645985c467ef0435@mail.gmail.com> <20060701051844.GE54876@cdnetworks.co.kr> <ef10de9a0606302333r40404013mb36bbaa5b91b9386@mail.gmail.com> <20060701070245.GF54876@cdnetworks.co.kr> <ef10de9a0607010054w135a1789x4093cec9df7f8d36@mail.gmail.com> <20060703082104.GB64457@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
--KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 03, 2006 at 05:21:04PM +0900, Pyun YongHyeon wrote: > On Sat, Jul 01, 2006 at 02:54:01AM -0500, Nikolas Britton wrote: > > On 7/1/06, Pyun YongHyeon <pyunyh@gmail.com> wrote: > > >On Sat, Jul 01, 2006 at 01:33:51AM -0500, Nikolas Britton wrote: > > > > On 7/1/06, Pyun YongHyeon <pyunyh@gmail.com> wrote: > > > > >On Fri, Jun 30, 2006 at 11:39:14PM -0500, Nikolas Britton wrote: > > > > > > On 6/30/06, Pyun YongHyeon <pyunyh@gmail.com> wrote: > > > > > > >On Thu, Jun 29, 2006 at 10:53:52PM -0500, Nikolas Britton wro= te: > > > > > > > > Anyone know what's going on with YukonII support in FreeBS= D, > > > > > > > > specifically the Marvell chips used in PCI-Express add-on = cards? > > > > > > > > > > > > > > > > Last I checked somebody was developing an experimental dri= ver=20 > > > and > > > > > > > > Marvell had just released the code to their FreeBSD 5.x/6.= x=20 > > > 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 t= here > > > > > > >is no possibility that Marvell releases their chip documentat= ions. > > > > > > > > > > > > > > > > > > > Marvell will give you the docs if you sign an NDA, I know it's= =20 > > > stupid > > > > > > but I think it's the only way... unless we vote with the walle= t...=20 > > > Who > > > > > > has PCI-Express gigabit NIC cards that meet the following crit= eria?: > > > > > > > > > > > > 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) dr= iver > > > > >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 d= river. > > > > > > > > > > > > > Will TCP Segmentation Offloading help if you already use a 9000 by= te > > > > mtu, and is it going to be supported, someday, with em(4)/bge(4)?.= =2E. > > > > 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=3D111662994600001&r=3D1&w=3D2 > > > > >=20 > > I see... A poor mans jumbo frames, but only works with the sender, >=20 > You may have to get a NIC that supports JUMBO frames on receiver > too unless your switch/bridge system fragments the JUMBO frames > into standard MTU frames. >=20 > > 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... > >=20 >=20 > Yes, we may borrow the code from NetBSD implementation but I can't > sure we can just copy it. I guess we need careful reexamination > the TSO effect on our TCP stack. >=20 Be sure to discuss this with Andre, according to page 9 of his EuroBSDCon paper he has some plans in this area: http://people.freebsd.org/~andre/Optimizing%20the%20FreeBSD%20IP%20and%20TC= P%20Stack.pdf - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEqPZCbHYXjKDtmC0RAmXSAKDfYPB1CCW+uoD3x6nT9q9PKjiDmwCfQp0a 4hQenk9NEktcCE9OXIihFzE= =mi78 -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060703104938.GA4468>