From owner-freebsd-net Fri Jul 5 13:21:36 2002 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 B860437B400 for ; Fri, 5 Jul 2002 13:21:33 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C6EC43E31 for ; Fri, 5 Jul 2002 13:21:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA00655; Fri, 5 Jul 2002 16:11:37 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g65KB7929339; Fri, 5 Jul 2002 16:11:07 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15653.64859.690620.421707@grasshopper.cs.duke.edu> Date: Fri, 5 Jul 2002 16:11:07 -0400 (EDT) To: John Polstra Cc: net@freebsd.org Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) 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> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Polstra writes: > In article <15653.62134.521004.349089@grasshopper.cs.duke.edu>, > Andrew Gallatin 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