From: rshriram@cs.ubc.ca
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com
Subject: [PATCH 0 of 5] Remus/Libxl: Network buffering support
Date: Sun, 25 Aug 2013 16:45:13 -0700 [thread overview]
Message-ID: <patchbomb.1377474313@athos.nss.cs.ubc.ca> (raw)
This patch series adds support for network buffering in the Remus
codebase in libxl.
The series is organized as follows:
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
next reply other threads:[~2013-08-25 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 23:45 rshriram [this message]
2013-08-25 23:45 ` [PATCH 1 of 5] remus: add libnl3 dependency to autoconf scripts rshriram
2013-08-26 9:06 ` Andrew Cooper
2013-08-27 8:44 ` Ian Campbell
2013-08-27 10:56 ` Ian Campbell
2013-08-29 19:13 ` Shriram Rajagopalan
2013-08-25 23:45 ` [PATCH 2 of 5] tools/hotplug: Remus network buffering setup scripts rshriram
2013-08-25 23:45 ` [PATCH 3 of 5] tools/libxl: setup/teardown Remus network buffering rshriram
2013-08-26 22:13 ` Andrew Cooper
2013-08-25 23:45 ` [PATCH 4 of 5] tools/libxl: Control network buffering in remus callbacks rshriram
2013-08-26 22:28 ` Andrew Cooper
2013-08-29 21:49 ` Shriram Rajagopalan
2013-08-30 8:42 ` Andrew Cooper
2013-08-25 23:45 ` [PATCH 5 of 5] tools/xl: Remus - Network buffering cmdline switch rshriram
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=patchbomb.1377474313@athos.nss.cs.ubc.ca \
--to=rshriram@cs.ubc.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.