On Thu, Aug 29, 2013 at 6:16 PM, Shriram Rajagopalan <rshriram@cs.ubc.ca>wrote:

> This patch series adds support for network buffering in the Remus
> codebase in libxl.
>
> Changes in V2:
> [1/5] Configure script will automatically enable/disable network
>       buffer support depending on the availability of the appropriate
>       libnl3 version. [If libnl3 is unavailable, a warning message will be
>       printed to let the user know that the feature has been disabled.]
>
>       use macros from pkg.m4 instead of pkg-config commands
>       removed redundant checks for libnl3 libraries.
>
> [3,4/5] - Minor nits.
>
> Version 1:
>
>  1/5 - changes to autoconf scripts to check for libnl3. Add linker flags
>        to libxl Makefile.
>
>  2/5 - External script to setup/teardown network buffering using libnl3's
> CLI.
>        This script will be invoked by libxl before starting Remus. The
> script's
>        main job is to bring up an IFB device with plug qdisc attached to
> it.
>        It then re-routes egress traffic from the guest's vif to the IFB
> device.
>
>  3/5 - Libxl code to invoke the external setup script, followed by
>        netlink related setup to obtain a handle on the output buffers
> attached
>        to each vif.
>
>  4/5 - Libxl interaction with network buffer module in the kernel via
> libnl3 API.
>
>  5/5 - xl cmdline switch to explicitly enable network buffering when
> starting remus.
>
>
> Few things to note:
> a) Based on previous email discussions, the setup/teardown task has been
> moved to a
>    hotplug style shell script which can be customized as desired, instead
> of
>    implementing it as C code inside libxl.
>
> b) Libnl3 is not available on NetBSD. Nor is it available on CentOS
> (Linux).
>    So I have made network buffering support an optional feature so that it
> can be
>    disabled if desired.
>
> c) NetBSD does not have libnl3. So I have put the setup script under
>    tools/hotplug/Linux folder.
>
> thanks
> shriram
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

ping!

shriram