Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932101AbWEIXdS (ORCPT ); Tue, 9 May 2006 19:33:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932100AbWEIXdS (ORCPT ); Tue, 9 May 2006 19:33:18 -0400 Received: from 216-99-217-87.dsl.aracnet.com ([216.99.217.87]:38786 "EHLO sous-sol.org") by vger.kernel.org with ESMTP id S932072AbWEIXdR (ORCPT ); Tue, 9 May 2006 19:33:17 -0400 Date: Tue, 9 May 2006 16:35:43 -0700 From: Chris Wright To: David Boutcher Cc: Christian Limpach , chrisw@sous-sol.org, Herbert Xu , ian.pratt@xensource.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, virtualization@lists.osdl.org, xen-devel@lists.xensource.com Subject: Re: [Xen-devel] [RFC PATCH 34/35] Add the Xen virtual network device driver. Message-ID: <20060509233543.GG24291@moss.sous-sol.org> References: <20060509140027.GD7834@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 899 Lines: 19 * David Boutcher (boutcher@us.ibm.com) wrote: > Then make a generic solution. VMWare supports migration, the Power > virtualization will get around to it eventually. All will need something > similar. So either make a common user-land tool, or (if you insist on > incorrectly driving this into the kernel) add some kind of common hook to > the TCP/IP stack. I'm not that fond of the in-kernel solution either. HA failover does this stuff in userspace, and has the same gratuitous arp requirements. Perhaps we should see some numbers showing the migration latency introduced. At the very least, it's easy to factor out as suggested. thanks, -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/