Date: Thu, 6 Jan 2011 14:17:17 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Jeff Roberson <jroberson@jroberson.net> Cc: arch@freebsd.org Subject: Re: Linux kernel compatability Message-ID: <20110106140722.E14966@maildrop.int.zabbadoz.net> In-Reply-To: <alpine.BSF.2.00.1101031343210.1450@desktop> References: <82826.1294088199@critter.freebsd.dk> <alpine.BSF.2.00.1101031343210.1450@desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
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. I hadn't quite liked the sys/cddl but given that we had sys/gnu as well. And then there is sys/compat. I wonder if you could still or maybe not make the shim layer something like it's own .ko kind of like opensolaris.ko (you cannot name it linux.ko though;) I guess similarly things in user space might go to contrib as well? Would you by any chance be able to generate a patch for all the sys/ and config etc. changes outside the ofed directory for prior review by people? I am just fearing that there might be bits for the V_irtualization side etc to consider, as might be for others with outstanding work. Thanks, /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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110106140722.E14966>