search for: sch_plug

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 and then calls the commit method of BufferedNIC after it gets the acknowledgement

...emy/xen.git linux Done the checkouts for 2.6.32-5 and everything seems to be perfectly fine. Remus does need some kernel configuration options to be enabled in order to work later on, reference here: http://wiki.xen.org/xenwiki/Remus. I can actually enable all of the options except one: CONFIG_NET_SCH_PLUG=m. There seems to be no such option, which is also missing in the Debian kernel and displays the folowing error: # remus <command stuff> Traceback (most recent call last): ....... raise BufferedNICException(''could not load sch_plug_module'') xen.remus.device.BufferedN...

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now