From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [PATCH 0 of 4 RFC] xl - Remus network buffering support
Date: Thu, 25 Jul 2013 00:09:26 -0700 [thread overview]
Message-ID: <patchbomb.1374736166@athos.nss.cs.ubc.ca> (raw)
This patch series adds support for network buffering in the Remus
codebase in xl/libxl. In previous emails, I had proposed for a script
invocation to setup network buffering. After digging through libnl API,
I managed to find most of what I needed (except for one command, which
right now is executed through system() call).
The patch series in its current state would allow xl to dynamically setup
and teardown buffering devices, qdiscs, etc associated with the guest,
instead of resorting to clunky one time configurations.
The series is organized as follows:
1/4 - Network buffering setup functions - abstractions built on top of libnl3 API
to implement functionality such as add/delete qdisc, interface up/down,
search for free ifb devices, etc.
2/4 - xl cmdline utility uses these abstractions to setup network buffers and
provides libxl with a list of ifb devices where packets would be buffered
3/4 - Libxl interaction with network buffer module in the kernel via libnl3.
4/4 - adds libnl3 (>= v3.2.17) dependency to autoconf scripts and linker flags
in tools/libxl/Makefile.
Functionality tested on debian squeeze (kernel 3.4) + openvswitch + 64-bit PV domU (kernel 3.4).
Couple of things to note:
1. I am not well versed with the autoconf stuff. I fixed the configure.ac
as best as I could. However, the libxl/Makefile patching is still clunky
[hard coded -I/usr/local/include/libnl3..]
2. I have kept most of the setup related C code in a separate file, that
I am also planning to submit to libvirt mailing list. Other toolstacks can choose to
setup network buffers in their own way (scripts or a different implementation).
As long as libxl gets as input a list of IFB devices to act on, things are good.
The code to control the network buffer, when Remus is operational,
is incorporated into libxl in the remus callbacks. This is something that only libxl
can do and [should do].
thanks
shriram
next reply other threads:[~2013-07-25 7:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 7:09 Shriram Rajagopalan [this message]
2013-07-25 7:09 ` [PATCH 1 of 4 RFC] xl/remus : Network buffering setup helper functions Shriram Rajagopalan
2013-07-29 15:42 ` Ian Campbell
2013-07-29 18:00 ` Shriram Rajagopalan
2013-07-30 10:44 ` Ian Campbell
2013-07-25 7:09 ` [PATCH 2 of 4 RFC] xl/remus: Network buffering cmdline switch, setup/teardown Shriram Rajagopalan
2013-07-29 15:49 ` Ian Campbell
2013-07-29 19:00 ` Shriram Rajagopalan
2013-07-30 10:50 ` Ian Campbell
2013-07-30 15:25 ` Shriram Rajagopalan
2013-07-30 15:39 ` Ian Campbell
2013-07-25 7:09 ` [PATCH 3 of 4 RFC] xl/remus: Control network buffering in remus callbacks Shriram Rajagopalan
2013-07-29 16:06 ` Ian Campbell
2013-08-07 15:41 ` Ian Jackson
2013-08-07 15:38 ` Ian Jackson
2013-08-07 21:51 ` Shriram Rajagopalan
2013-08-08 11:07 ` Ian Jackson
2013-07-25 7:09 ` [PATCH 4 of 4 RFC] xl/remus: Add libnl3 dependency to autoconf scripts and libxl/Makefile Shriram Rajagopalan
2013-07-26 9:44 ` Wen Congyang
2013-07-26 13:51 ` Shriram Rajagopalan
2013-07-26 9:56 ` David Vrabel
2013-07-26 13:56 ` Shriram Rajagopalan
2013-07-29 5:58 ` Wen Congyang
2013-07-29 13:07 ` Shriram Rajagopalan
2013-07-29 15:41 ` David Vrabel
2013-07-30 16:11 ` [PATCH 0 of 4 RFC] xl - Remus network buffering support Roger Pau Monné
2013-07-31 8:33 ` Ian Campbell
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.1374736166@athos.nss.cs.ubc.ca \
--to=rshriram@cs.ubc.ca \
--cc=ian.campbell@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 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).