[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Remus' Network Buffering



On Thu, Apr 19, 2012 at 9:15 AM, Rahul Singh <singh.rahul.1983@xxxxxxxxx> wrote:

Hi,
I am trying to understand and change the network buffering that is being used by Remus, the HA solution present in Xen. From what i understood from reading the code, Remus calls the postsuspend method of the BufferedNIC after it suspends the domain that sends TC_PLUG_CHECKPOINT message and start the buffering

for packets in the "next" epoch [the one that starts after the domain is resumed]
 

and then calls the commit method of BufferedNIC after it gets the acknowledgement that sends the TC_PLUG_RELEASE message and releases the buffered packets.

of the previous current epoch [the one whose checkpoint was just committed on the backup machine]
 

I have the following doubts
1) How does remus ensure that the packets gets buffered for an entire epoch ?

2) If i comment out the lines in the "postsuspend" and "commit" lines of the BufferedNIC class that send the TC_PLUG_CHECKPOINT and TC_PLUG_RELEASE, i see that all the network packets are being buffered and i cannot ping the Remus-protected VM at all. Where is the packet buffering happen if i comment out these 2 lines ?


the module starts out in the buffered mode and releases packets only upon receiving a RELEASE command.

hope that helps.

cheers
shriram
 

Thanking you,
Rahul.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.