From owner-freebsd-xen@FreeBSD.ORG Mon Jan 31 23:57:06 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 462A9106566B for ; Mon, 31 Jan 2011 23:57:06 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id 1BAD18FC21 for ; Mon, 31 Jan 2011 23:57:05 +0000 (UTC) Received: from [192.168.4.138] (207-225-98-3.dia.static.qwest.net [207.225.98.3]) (authenticated bits=0) by aslan.scsiguy.com (8.14.4/8.14.4) with ESMTP id p0VNupVZ075631 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 16:56:52 -0700 (MST) (envelope-from gibbs@FreeBSD.org) Message-ID: <4D474C3F.1010407@FreeBSD.org> Date: Mon, 31 Jan 2011 16:56:47 -0700 From: "Justin T. Gibbs" Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110123 Thunderbird/3.1.8 MIME-Version: 1.0 To: Janne Snabb References: <1295969742.3187.48.camel@pow> In-Reply-To: X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (aslan.scsiguy.com [70.89.174.89]); Mon, 31 Jan 2011 16:56:53 -0700 (MST) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@FreeBSD.org, luke@hybrid-logic.co.uk Subject: Re: I have a problem with iSCSI on AMD64 Xen HVM X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gibbs@FreeBSD.org List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 23:57:06 -0000 On 1/25/2011 6:30 PM, Janne Snabb wrote: > > (I wish there was a bit more comments in the non-obvious parts of > the code. Now it is difficult for a FreeBSD/Xen PV newbie to work > on it without intimate knowledge of the history of the odd bits of > the code. It clearly needs more care than what it is being given > now. Things like the "do something useful" panic also indicate that > there is no more than few people who actually play with and try out > the code currently.) Xen use models in our community are quite varried and that is reflected in the relative stability and quality of the different areas of FreeBSD's Xen support. In my day job at SpectraLogic, we rely heavily on FreeBSD's amd64 HVM Xen support, but only for serving block storage. While we've invested heavily in the PV driver framework and the blkback driver (and to a lesser extent blkfront), we haven't done much to netfront since it is not a road block for developing our product. There are only so many hours in the day... :-) It seems that the use of Xen in FreeBSD is increasing, so I'm hopeful more folks will step forward to improve other areas of our Xen support. I sympathize with your desire for more code comments to make it easier to ramp up on Xen. Unfortunately, there is little documentation about Xen other than the "Linux reference implementation", and it is usually quite terse in the comments department. I've done my best to improve this situation in the areas on which I've worked. Hopefully others will do the same and perhaps even give netfront the rewrite it deserves. -- Justin