From owner-freebsd-net@FreeBSD.ORG Fri Apr 7 00:33:57 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 0BCB916A400 for ; Fri, 7 Apr 2006 00:33:57 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outbound7.internet-mail-service.net (outbound7.internet-mail-service.net [216.240.47.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5EEB43D48 for ; Fri, 7 Apr 2006 00:33:55 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by outbound.internet-mail-service.net (Postfix) with ESMTP id E158B249BA6; Thu, 6 Apr 2006 17:33:54 -0700 (PDT) Received: from [10.251.19.131] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id k370XsUX025204; Thu, 6 Apr 2006 17:33:54 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <4435B36B.4080608@elischer.org> Date: Thu, 06 Apr 2006 17:33:47 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John-Mark Gurney References: <2a41acea0604061648g83646aeme8792b6cf27f61b5@mail.gmail.com> <20060407002647.GT53811@funkthat.com> In-Reply-To: <20060407002647.GT53811@funkthat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net , Jack Vogel Subject: Re: using uipc_jumbo.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 00:33:57 -0000 John-Mark Gurney wrote: >Jack Vogel wrote this message on Thu, Apr 06, 2006 at 16:48 -0700: > > >>At the moment I am making Packet Split work for the em driver, but >>in a quick look around I cant see how the uipc_jumbo code gets >>compiled. I realize its been wedded to the ti driver, but I want to >>build and link against the kernel code without that driver. >> >>Anyone who understands all the inner workings of the build system >>want to give me a quick answer on the best way to do this? I mean >>I could probably heavy-handedly whack the Makefile, but I want >>the way to do it that would be 'correct' :) >> >> > >uipc_jumbo has been retired.. you should use the mbuf jumbo api >instead... You just need to provide MJUMPAGESIZE, MJUM9BYTES, or >MJUM16BYTES to m_getjcl to get the buffer... It appears that it >hasn't been documented in the mbuf(9) manpage yet though.. > > though as you are probably trying to make a driver that runs on older kernels too, that's probably not great news.