From owner-freebsd-net Fri Jul 5 12:37:14 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 DC87537B400 for ; Fri, 5 Jul 2002 12:37:11 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFBB843E31 for ; Fri, 5 Jul 2002 12:37:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g65Jb6T69530; Fri, 5 Jul 2002 12:37:06 -0700 (PDT) (envelope-from jdp@vashon.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.12.4/8.12.4/Submit) id g65Jb6rm003934; Fri, 5 Jul 2002 12:37:06 -0700 (PDT) (envelope-from jdp) Date: Fri, 5 Jul 2002 12:37:06 -0700 (PDT) Message-Id: <200207051937.g65Jb6rm003934@vashon.polstra.com> To: net@freebsd.org From: John Polstra Cc: gallatin@cs.duke.edu Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) In-Reply-To: <15653.62134.521004.349089@grasshopper.cs.duke.edu> References: <20020619090046.A2063@panzer.kdm.org> <20020705132735.A873@unixdaemons.com> <200207051747.g65HliO2003668@vashon.polstra.com> <15653.62134.521004.349089@grasshopper.cs.duke.edu> Organization: Polstra & Co., Seattle, WA 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 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. In other words, I doubt that the bge driver could use a new buffer API unless it provided a way to get physically contiguous buffers. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message