From: Jason Luan <luanjianhai@163.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@suse.com>
Subject: Re: xen-netback notify DomU to send ARP.
Date: Mon, 14 Jan 2013 21:39:59 +0800 [thread overview]
Message-ID: <50F40AAF.8050105@163.com> (raw)
In-Reply-To: <1358165788.14683.13.camel@zakaz.uk.xensource.com>
于 2013年01月14日 20:16, Ian Campbell 写道:
> On Sun, 2013-01-13 at 01:51 +0000, Jason Luan wrote:
>> Hi Ian,
>> The patch only notify around peer how to reach it when network
>> circumstance changed.
>> I don't know what's wrong about the patch (the new feature isn't
>> proper or the patch have other problem)?
> I think the main remaining concern is Jan's regarding what effect this
> patch will have upon the various existing netfront's out in the wild.
>
> Have you considered the behaviour of various distro kernels, and the
> pvops and classic-Xen trees?
Because the patch fix intern bug of oracle bug queue, I have test some
netfontends( v2.6.32, v2.6.39 and
the latest kernel of Ubuntu 1104 ) on variable netbackend ( v2.6.18,
v2.6.32 and v2.6.39) for more time, no
other issue be found.
But i don't test classic-xen trees, i will test for whole day at tomorrow.
>
> I don't mind if older kernels fail to ARP on this new transition (they
> are no worse off than now) but if they crash or something that might be
> an issue.
Yes, you are right. But if no other issue be introduced, sending
gratuitous ARP initiative will be better.
So, Our trouble is which issue will be introduced by the patch at now? I
don't found until now. If you have
already thought of some bug, would you like to tell me. I will try to
fix it.
>
>> Why do any body ask the issue?
Sorry, It is typo (ask should be ack).
> What do you mean?
>
> Ian.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
Thanks,
Jason
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-14 13:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 11:57 xen-netback notify DomU to send ARP jianhai luan
2013-01-08 13:13 ` [Xen-devel] " Jan Beulich
2013-01-08 13:42 ` Ian Campbell
2013-01-08 15:40 ` jianhai luan
2013-01-08 16:00 ` [Xen-devel] " Ian Campbell
2013-01-09 1:07 ` Jason Luan
2013-01-09 12:03 ` [Xen-devel] " Ian Campbell
2013-01-09 7:39 ` jianhai luan
2013-01-09 10:06 ` Jan Beulich
2013-01-09 12:28 ` jianhai luan
2013-01-09 13:44 ` Jan Beulich
2013-01-09 15:37 ` Jason Luan
2013-01-09 15:44 ` [Xen-devel] " Jan Beulich
[not found] ` <50ED950A.6010203@163.com>
2013-01-09 16:25 ` Jan Beulich
[not found] ` <50EDA624.1010008@163.com>
2013-01-10 7:00 ` [Xen-devel] " jianhai luan
2013-01-10 15:20 ` Jason Luan
2013-01-13 1:51 ` Jason Luan
2013-01-14 12:16 ` Ian Campbell
2013-01-14 13:39 ` Jason Luan [this message]
2013-01-14 14:24 ` Jan Beulich
2013-01-14 14:43 ` Jason Luan
2013-01-14 15:52 ` Jan Beulich
[not found] ` <50EF7106.7000302@oracle.com>
2013-01-21 7:26 ` [V2] " jianhai luan
2013-01-21 11:04 ` David Vrabel
2013-01-21 11:33 ` Jason Luan
2013-01-21 11:55 ` Jan Beulich
2013-01-21 12:23 ` Ian Campbell
2013-01-21 12:30 ` Ian Campbell
2013-01-21 12:38 ` Jason Luan
2013-01-21 13:49 ` Jason Luan
2013-01-21 13:52 ` Ian Campbell
2013-01-21 14:02 ` Jason Luan
2013-01-21 14:09 ` Ian Campbell
2013-01-21 14:16 ` Jan Beulich
2013-01-21 14:31 ` Jason Luan
2013-01-21 14:54 ` Jason Luan
2013-01-21 15:20 ` Jan Beulich
2013-01-21 15:30 ` Jason Luan
2013-01-21 15:44 ` Jan Beulich
2013-01-21 15:56 ` Jason Luan
2013-01-21 15:59 ` Jan Beulich
2013-01-21 16:02 ` Jason Luan
2013-01-21 15:59 ` Ian Campbell
2013-01-21 12:25 ` Jason Luan
-- strict thread matches above, loose matches on Subject: below --
2013-01-09 15:07 Jason Luan
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=50F40AAF.8050105@163.com \
--to=luanjianhai@163.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.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 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).