Date: Thu, 6 Jan 2011 13:17:57 -1000 (HST) From: Jeff Roberson <jroberson@jroberson.net> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-arch@FreeBSD.org Subject: Re: Linux kernel compatability Message-ID: <alpine.BSF.2.00.1101061314040.1450@desktop> In-Reply-To: <20110106222945.R14966@maildrop.int.zabbadoz.net> References: <82826.1294088199@critter.freebsd.dk> <alpine.BSF.2.00.1101031343210.1450@desktop> <20110106140722.E14966@maildrop.int.zabbadoz.net> <4D260E0D.8080003@bsdimp.com> <20110106222945.R14966@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Jan 2011, Bjoern A. Zeeb wrote: > On Thu, 6 Jan 2011, Warner Losh wrote: > >> On 01/06/2011 07:17, Bjoern A. Zeeb wrote: >>> On Mon, 3 Jan 2011, Jeff Roberson wrote: >>> >>>> Unfortunately it would create quite a lot of code churn as there are >>>> relatively few that are minorly different. You can page through the >>>> wrapper code if you're interested. >>>> >>>> http://svn.freebsd.org/viewvc/base/projects/ofed/head/sys/ofed/include/linux/ >>> >>> One thing I am not too sure about is sys/ofed. Given the entire >>> discussions it might well be better suited in sys/contrib/ofed under >>> the assumtion that the code is mostly maintained outside our tree and >>> we get in occational updates. >> >> If you look at what Jeff has done, you'll see that the external code >> follows our standards of residing in sys/contrib/ofed, while the code that >> glues it into the tree is in sys/ofed. > > I might just be too blind to see an ofed there: > http://svn.freebsd.org/viewvc/base/projects/ofed/head/sys/contrib/ > > It's rdma I guess. It feels just awkward to have the glue in > sys/mumble rather than completely bundled in sys/contrib/ofed/** like > we do for ipfilter, pf, ... to my understanding. > > The real glue into our stack, I assume, sits in net*/* mostly. That rdma was existing for iwarp stubs. I expect it will go away when chelsio finishes integrating with the ofed work for full iwarp support. I have the code in sys/ofed but it could easily be moved to sys/contrib/ofed. That is probably more appropriate. I was thinking just ofed as it was another native network like netinet, netatalk, netipx, etc. It perhaps would have been more appropriate to call it infiniband/. The extra directory is not a real problem either way. > > >>> I guess similarly things in user space might go to contrib as well? >> src/contrib is for code that's maintained outside the source tree that we >> adapt. > > Are all user space tools hand-rolled or are they ported over as well? > All userspace tools are ported in contrib/ofed. Only minor changes were required to build on BSD. We have a very complete stack. I know of no feature that is missing. > > Maybe I should wait till Jeff will post the diff to see. I don't mind discussing the technical points further at all. I just don't feel I have any more to add about the more existential topics. Thanks, Jeff > > /bz > > -- > Bjoern A. Zeeb You have to have visions! > <ks> Going to jail sucks -- <bz> All my daemons like it! > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1101061314040.1450>