From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 19 20:56:46 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C75A106567A for ; Thu, 19 Feb 2009 20:56:46 +0000 (UTC) (envelope-from prvs=julian=2945f491c@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 84E0A8FC17 for ; Thu, 19 Feb 2009 20:56:46 +0000 (UTC) (envelope-from prvs=julian=2945f491c@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.36]) by smtp-outbound.ironport.com with ESMTP; 19 Feb 2009 12:28:21 -0800 Message-ID: <499DC0F7.10709@elischer.org> Date: Thu, 19 Feb 2009 12:28:39 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: FreeBSD virtualization mailing list , Marko Zec , "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Vimage next step X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 20:56:47 -0000 I've been doing performance testing on the 'non-vimage' 'structified' case VS the original 'globals' case and have not been able to see any really significant differences (though I have seen very slight differences in the distribution of results). SO I think we are in the position of moving forward to the next steps. I think that just means checking in the rest of the vimage tree from what I have seen. Then we can play with it a bit and then proceed to the jail/vimage merge stuff that Jamie (and bz) are working on. One thing I'd like to do is make the following changes: 1/ evaluate the ordering of teh items in the vimage structures to see if there are items that should be clusterred for cache reasons. 2/ remove all sub structures from the vimage structures and replace them with pointers. This is because puting them in directly in the vimage structures will make our lives harder due to ABI issues. If they are independently allocated (*) then we don't need to worry about them changing in size. (*) actually they could still be allocated as a blob but we would access them as if they are separate. comments? Julian