All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Graham, Simon" <Simon.Graham@stratus.com>,
	xen-devel@lists.xensource.com
Subject: Re: arp during live migration
Date: Wed, 07 Mar 2007 16:02:02 +0000	[thread overview]
Message-ID: <C214927A.AC93%keir@xensource.com> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767104DC4135@EXNA.corp.stratus.com>




On 6/3/07 22:59, "Graham, Simon" <Simon.Graham@stratus.com> wrote:

> All of this leads to a ~1s delay setting up the network path plus the
> gratuitous ARP is dropped so there can be a MUCH larger network
> blackout. If you are trying to get sub-second blackout on migration this
> is a big problem!
> 
> It seems to me that the right thing to do here is to have the link up on
> the VIF in advance of the domain resuming on the target but I'm guessing
> that this would cause netback to have conniptions...

Changeset 14280 in xen-unstable fixes this by no longer using the
netif_carrier flag. The patch will probably backport very straightforwardly
onto older (or newer) 2.6 Linux kernels.

 -- Keir

  parent reply	other threads:[~2007-03-07 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 22:22 arp during live migration Graham, Simon
2007-03-03 16:21 ` Jacob Gorm Hansen
2007-03-03 17:10   ` Graham, Simon
2007-03-05 15:40   ` Cristian Zamfir
     [not found] ` <1172938895.14470.25.ca mel@localhost.localdomain>
2007-03-05 23:47   ` Graham, Simon
2007-03-06 22:59   ` Graham, Simon
2007-03-07  8:30     ` Keir Fraser
2007-03-07 16:02     ` Keir Fraser [this message]
2007-03-07 22:25       ` Graham, Simon
2007-03-08  7:53         ` Keir Fraser
2008-01-30 11:17 ` Hans-Christian Armingeon
  -- strict thread matches above, loose matches on Subject: below --
2007-03-02 20:54 Cristian Zamfir

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=C214927A.AC93%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Simon.Graham@stratus.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.