netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jianhai luan <jianhai.luan@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, netdev@vger.kernel.org,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: xen-netback notify DomU to send ARP.
Date: Tue, 08 Jan 2013 19:57:17 +0800	[thread overview]
Message-ID: <50EC099D.6020407@oracle.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Hi,
   When Xen Dom0's network circumstance changed, DomU
should be notified in some special condition. For
example the below circumstance:
   ping from Guest A to DomU:
   Guest A --> eth0 - bond0 - xenbr0 --VIF(DOMU)
               eth1 /
   when eth0 inactive, and eth1 active.
   Guest A --> eth0   bond0 - xenbr0 --VIF(DOMU)
               eth1 /
   Guest A will don't reach to DomU. After Guest A
   send ARP request and DomU respond, Guest A will
   reach DomU. But some more second will be elapsed.
               eth0   bond0 - xenbr0 --VIF(DOMU)
   Guest A --> eth1/

If Xen netback watch the network change, will notify
DomU by change it own status. So netfront will watch
netback's change, and DomU send ARP initiative.

Thanks,
Jason

[-- Attachment #2: .0001-xen-netback-notify-DomU-to-send-ARP.patch.swp --]
[-- Type: application/octet-stream, Size: 12288 bytes --]

             reply	other threads:[~2013-01-08 11:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 11:57 jianhai luan [this message]
2013-01-08 13:13 ` [Xen-devel] xen-netback notify DomU to send ARP 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>
     [not found]                       ` <50EDA80002000078000B427B@nat28.tlf.novell.com>
     [not found]                         ` <50EDA624.1010008@163.com>
2013-01-10  7:00                           ` jianhai luan
     [not found]                             ` <50EF7106.7000302@oracle.com>
     [not found]                               ` <50FCED9F.1050708@oracle.com>
     [not found]                                 ` <50FD3AB202000078000B7CD5@nat28.tlf.novell.com>
     [not found]                                   ` <1358770987.3279.196.camel@zakaz.uk.xensource.com>
2013-01-21 12:38                                     ` [V2] " 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=50EC099D.6020407@oracle.com \
    --to=jianhai.luan@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=netdev@vger.kernel.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).