From: Dan Smith <danms@us.ibm.com>
To: containers@lists.osdl.org
Cc: netdev@vger.kernel.org, orenl@librato.com
Subject: C/R: Network namespace and device support (v2)
Date: Fri, 22 Jan 2010 13:09:49 -0800 [thread overview]
Message-ID: <1264194592-7529-1-git-send-email-danms@us.ibm.com> (raw)
This set adds support for checkpointing network namespaces and devices,
with in-kernel restart.
Basic support includes veth pair and loopback adapters and allows me to
checkpoint and restart a containerized copy of sendmail with a veth
bridged to a physical network. Follow-on work is detailed in the header
of the last patch.
Changes in v2 only to the final patch, detailed there.
next reply other threads:[~2010-01-22 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 21:09 Dan Smith [this message]
2010-01-22 21:09 ` [PATCH 1/3] Expose rtnl_link_ops_get() Dan Smith
2010-01-22 21:09 ` [PATCH 2/3] Add a veth_get_peer() and veth_set_peer() functions Dan Smith
2010-01-22 21:09 ` [PATCH 3/3] C/R: Basic support for network namespaces and devices (v2) Dan Smith
2010-01-23 9:25 ` David Miller
[not found] ` <20100123.012537.99190542.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-01-23 15:19 ` Dan Smith
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=1264194592-7529-1-git-send-email-danms@us.ibm.com \
--to=danms@us.ibm.com \
--cc=containers@lists.osdl.org \
--cc=netdev@vger.kernel.org \
--cc=orenl@librato.com \
/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).