From: Andi Kleen <ak@suse.de>
To: virtualization@lists.osdl.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>,
chrisw@sous-sol.org, ian.pratt@xensource.com,
xen-devel@lists.xensource.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [RFC PATCH 34/35] Add the Xen virtual network device driver.
Date: Tue, 9 May 2006 15:14:28 +0200 [thread overview]
Message-ID: <200605091514.29205.ak@suse.de> (raw)
In-Reply-To: <E1FdRpp-0008HG-00@gondolin.me.apana.org.au>
On Tuesday 09 May 2006 15:01, Herbert Xu wrote:
> Christian Limpach <Christian.Limpach@cl.cam.ac.uk> 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
next prev parent reply other threads:[~2006-05-09 13:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060509084945.373541000@sous-sol.org>
2006-05-09 7:00 ` [RFC PATCH 34/35] Add the Xen virtual network device driver Chris Wright
2006-05-09 11:55 ` [Xen-devel] " Herbert Xu
2006-05-09 12:43 ` Christian Limpach
2006-05-09 13:01 ` Herbert Xu
2006-05-09 13:14 ` Andi Kleen [this message]
2006-05-09 13:16 ` Christian Limpach
2006-05-09 13:26 ` Herbert Xu
2006-05-09 14:00 ` Christian Limpach
2006-05-09 14:30 ` [Xen-devel] " David Boutcher
2006-05-09 23:35 ` Chris Wright
2006-05-09 11:58 ` Christoph Hellwig
2006-05-09 23:37 ` Chris Wright
2006-05-09 18:56 ` Stephen Hemminger
2006-05-09 23:39 ` Chris Wright
2006-05-09 20:25 ` Stephen Hemminger
2006-05-09 20:26 ` Keir Fraser
2006-05-09 20:46 ` Roland Dreier
2006-05-10 18:28 ` Andi Kleen
2006-05-11 0:33 ` Herbert Xu
2006-05-11 7:49 ` Keir Fraser
2006-05-11 8:04 ` Herbert Xu
2006-05-11 9:47 ` Andi Kleen
2006-05-11 16:18 ` Stephen Hemminger
2006-05-11 16:48 ` Rick Jones
2006-05-11 17:30 ` Andi Kleen
2006-05-09 20:32 ` Chris Wright
2006-05-09 22:41 ` [Xen-devel] " Herbert Xu
2006-05-09 23:51 ` Chris Wright
2006-05-10 6:36 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200605091514.29205.ak@suse.de \
--to=ak@suse.de \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=chrisw@sous-sol.org \
--cc=herbert@gondor.apana.org.au \
--cc=ian.pratt@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).