Date: Fri, 5 Jul 2002 16:11:07 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Polstra <jdp@polstra.com> Cc: net@freebsd.org Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) Message-ID: <15653.64859.690620.421707@grasshopper.cs.duke.edu> In-Reply-To: <200207051937.g65Jb6rm003934@vashon.polstra.com> References: <20020619090046.A2063@panzer.kdm.org> <20020705132735.A873@unixdaemons.com> <200207051747.g65HliO2003668@vashon.polstra.com> <15653.62134.521004.349089@grasshopper.cs.duke.edu> <200207051937.g65Jb6rm003934@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra writes: > In article <15653.62134.521004.349089@grasshopper.cs.duke.edu>, > Andrew Gallatin <gallatin@cs.duke.edu> wrote: > > > WHOOPS, I'm afraid I have to correct myself. The BCM570x chips do > > > indeed support multiple buffers for jumbo packets. I'm sorry for the > > > earlier misinformation! > > > > Are programming docs for this board available? > > To get them you have to execute an NDA with Broadcom. So we're > effectively limited to what can be gleaned from the Linux driver. Its > header file has a struct declaration for the "T3_EXT_RCV_BD" (extended > receive buffer descriptor, probably) but the driver doesn't actually > use it. Without the docs it would take a lot of trial & error to > figure out how to make it work. Not necessarily. It just looked at the struct def. To me, it looks *exactly* like the equivalent tigon-2 struct. This makes sense, as its a descendant of the tigon-2. It should work just fine.. (easy for me to say, as I don't have a card to test it on). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15653.64859.690620.421707>