From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: consolidated xencomm Date: Thu, 16 Nov 2006 15:58:00 -0600 Message-ID: <1163714280.26011.79.camel@basalt> References: <1163692542.26011.14.camel@basalt> <1163700499.5529.9.camel@lappy> Reply-To: Hollis Blanchard Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1163700499.5529.9.camel@lappy> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alex Williamson Cc: xen-ppc-devel , xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, 2006-11-16 at 11:08 -0700, Alex Williamson wrote: > On Thu, 2006-11-16 at 09:55 -0600, Hollis Blanchard wrote: > > > > I think I'm missing something. Why did IA64 fork xencomm? > > > > I distinctly remember having conversations about sharing the code, which > > is obviously the right thing to do. > > Because Tristan believed the resulting amount of shared code would > actually be very small (1 file) and we wanted to get his work into the > tree before he left Bull. We can still work to share as much as > possible even with the code split. Thanks, This is the first I've heard of that conclusion. I was working with Tristan to share the code, and the last time we spoke (in Sep) we were discussing how "mini" descriptors may still be needed (on all xencomm architectures!) because of Linux modules. -- Hollis Blanchard IBM Linux Technology Center