From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 17 21:09:13 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B25E21065683 for ; Mon, 17 Mar 2008 21:09:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outD.internet-mail-service.net (outD.internet-mail-service.net [216.240.47.227]) by mx1.freebsd.org (Postfix) with ESMTP id 9597D8FC2D for ; Mon, 17 Mar 2008 21:09:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Mon, 17 Mar 2008 14:09:11 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id B4B212D6006; Mon, 17 Mar 2008 14:09:10 -0700 (PDT) Message-ID: <47DEDDF9.7010200@elischer.org> Date: Mon, 17 Mar 2008 14:09:13 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Matthew Dillon References: <20080316122108.S44049@fledge.watson.org> <200803162313.m2GNDbvl009550@apollo.backplane.com> <3c0b01820803171243k5eb6abd3y1e1c44694c6be0f6@mail.gmail.com> <200803172016.m2HKGfjA020263@apollo.backplane.com> In-Reply-To: <200803172016.m2HKGfjA020263@apollo.backplane.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Sack , jgordeev@dir.bg, "Andrey V. Elsukov" , Robert Watson , freebsd-hackers@freebsd.org Subject: Re: vkernel & GSoC, some questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Mar 2008 21:09:13 -0000 Matthew Dillon wrote: > In all three cases the emulated hardware -- disk and network basically, > devolves down into calling read() or write() or the real-kernel > equivalent. A hypervisor has the most work to do since it is trying to > emulate a hardware interface (adding another layer). XEN has less work > to do as it is really not trying to emulate hardware. A vkernel has > even less work to do because it is running as a userland program and can > simply make the appropriate system call to implement the back-end. And jails and similar have the absolute minimum.. at the cost of making a single accessible point of failure (the one kernel).