Date: Thu, 06 Apr 2006 17:33:47 -0700 From: Julian Elischer <julian@elischer.org> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: freebsd-net <freebsd-net@freebsd.org>, Jack Vogel <jfvogel@gmail.com> Subject: Re: using uipc_jumbo.c Message-ID: <4435B36B.4080608@elischer.org> In-Reply-To: <20060407002647.GT53811@funkthat.com> References: <2a41acea0604061648g83646aeme8792b6cf27f61b5@mail.gmail.com> <20060407002647.GT53811@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4435B36B.4080608>