From: Jason Luan <luanjianhai@163.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [V2] xen-netback notify DomU to send ARP.
Date: Mon, 21 Jan 2013 23:56:17 +0800 [thread overview]
Message-ID: <50FD6521.70101@163.com> (raw)
In-Reply-To: <50FD707602000078000B7F65@nat28.tlf.novell.com>
于 2013年01月21日 23:44, Jan Beulich 写道:
>>>> On 21.01.13 at 16:30, Jason Luan <luanjianhai@163.com> wrote:
>> 于 2013年01月21日 23:20, Jan Beulich 写道:
>>>>>> On 21.01.13 at 15:54, Jason Luan <luanjianhai@163.com> wrote:
>>>> About the patch, what test do i still need to do in the future?
>>>> Or just be internal patch(after all, OVM just support Linux, window and
>>>> Solaris ).
>>>>
>>>> Would you give me some advice?
>>> With the revised patch (only doing a Connected->Connected
>>> transition now) I don't think you need to do more testing - as
>>> said before, I do believe that frontends have to be capable to
>>> deal with that (but of course they need to be taught to send
>>> an ARP upon that pseudo-transition happening).
>> Linux frontend have deal with that, and i don't modify other system.
>> What will i do in the future?
> I don't understand what you're asking.
Sorry for that. I mean that what will be need to do about the patch ?
>
> Jan
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-21 15:56 UTC|newest]
Thread overview: 51+ 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:13 ` Jan Beulich
2013-01-08 13:42 ` Ian Campbell
2013-01-08 15:40 ` jianhai luan
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 10:06 ` Jan Beulich
2013-01-09 12:28 ` jianhai luan
2013-01-09 12:28 ` jianhai luan
2013-01-09 13:44 ` Jan Beulich
2013-01-09 13:44 ` Jan Beulich
2013-01-09 15:37 ` Jason Luan
2013-01-09 15:44 ` [Xen-devel] " Jan Beulich
2013-01-09 15:44 ` 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
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 ` [Xen-devel] " Jason Luan
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 [this message]
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
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=50FD6521.70101@163.com \
--to=luanjianhai@163.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 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.