Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750988AbWEINOi (ORCPT ); Tue, 9 May 2006 09:14:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750997AbWEINOh (ORCPT ); Tue, 9 May 2006 09:14:37 -0400 Received: from mx1.suse.de ([195.135.220.2]:55684 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1750974AbWEINOg (ORCPT ); Tue, 9 May 2006 09:14:36 -0400 From: Andi Kleen To: virtualization@lists.osdl.org Subject: Re: [Xen-devel] [RFC PATCH 34/35] Add the Xen virtual =?utf-8?q?network=09device=09driver=2E?= Date: Tue, 9 May 2006 15:14:28 +0200 User-Agent: KMail/1.9.1 Cc: Herbert Xu , Christian Limpach , chrisw@sous-sol.org, ian.pratt@xensource.com, xen-devel@lists.xensource.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605091514.29205.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1034 Lines: 24 On Tuesday 09 May 2006 15:01, Herbert Xu wrote: > Christian Limpach wrote: > > > > There's at least two reasons why having it in the driver is preferable: > > - synchronizing sending the fake ARP request with when the device is > > operational -- you really want to make this well synchronized to keep > > unreachability as short as possible, especially when doing live > > migration > > - anybody but the guest might not know (all) the MAC addresses for which > > to send a fake ARP request > > Sure. However, what's there to stop you from doing this in user-space > inside the guest? I guess they don't trust user space. But the standard ipup script from iproute2 does this already so at least for modern distributions it should just work. -Andi - 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/