From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
jbohac@suse.cz, netdev@vger.kernel.org, shemminger@vyatta.com
Subject: Re: IPv6: autoconfiguration and suspend/resume or link down/up
Date: Sat, 23 Jul 2011 16:31:21 +0200 [thread overview]
Message-ID: <4E2ADB39.9070409@gmail.com> (raw)
In-Reply-To: <20110722092159.GA20722@gondor.apana.org.au>
Le 22/07/2011 11:21, Herbert Xu a écrit :
> On Fri, Jul 22, 2011 at 01:06:28AM -0700, David Miller wrote:
>>
>> Suspend is even more important because while we were suspended we
>> could be on the same network but the routers present and available
>> might have changed completely.
>
> Unfortunately virtual machine live migration also uses the suspend
> & resume mechanism. In that case we don't wish to renegotiate
> everything, since the goal is to minimise the outage window.
>
> This would suggest that putting the policy in user-space may be the
> best option.
For the particular situation where we use suspend/resume to migrate a virtual machine, we might have
a kernel parameter or sysfs entry that instruct the kernel not to renegotiate anything on resume.
That being said, the time to renegotiate a network setup sounds very short, compared to the time for
a full suspend-migrate-resume cycle. I'm not sure VM migration would really suffer from such
renegotiation.
And because the local network may change while we migrate the VM (in particular if the migration
happens because of some failover), I think we should enforce renegotiation on resume anyway.
Nicolas.
next prev parent reply other threads:[~2011-07-23 14:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:02 IPv6: autoconfiguration and suspend/resume or link down/up Jiri Bohac
2011-07-20 16:15 ` Stephen Hemminger
2011-07-20 16:29 ` Jiri Bohac
2011-07-20 16:21 ` Dan Williams
2011-07-20 16:36 ` Jiri Bohac
2011-07-21 5:30 ` Dan Williams
2011-07-21 16:35 ` Dan Williams
2011-07-21 19:44 ` Stephen Hemminger
2011-07-22 8:06 ` David Miller
2011-07-22 9:21 ` Herbert Xu
2011-07-23 14:31 ` Nicolas de Pesloüan [this message]
2011-07-23 15:27 ` Herbert Xu
2011-07-23 16:37 ` Stephen Hemminger
2011-07-24 0:18 ` Herbert Xu
2011-07-24 8:35 ` Nicolas de Pesloüan
2011-07-25 3:26 ` Stephen Hemminger
2011-07-25 3:46 ` Herbert Xu
2011-07-27 19:48 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2011-07-19 19:42 Stephen Hemminger
2011-07-26 5:16 ` Anirban Chakraborty
2011-07-25 16:55 Stephen Hemminger
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=4E2ADB39.9070409@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jbohac@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).