From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen 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 Message-ID: <200605091514.29205.ak@suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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 Return-path: 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 To: virtualization@lists.osdl.org In-Reply-To: Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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