From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: weigelt-EU+a56NjgY8@public.gmane.org
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [Devel] [RFC] user-cr: Routing information in userspace
Date: Sat, 29 May 2010 11:09:45 -0700 [thread overview]
Message-ID: <87r5kua8ba.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: <20100529031349.GA10541-q9I3ByPDOfiE+EvaaNYduQ@public.gmane.org> (Enrico Weigelt's message of "Sat\, 29 May 2010 05\:13\:50 +0200")
EW> I'd prefer the routing tables being available via sysfs
EW> (eg. /sys/net/ipv4/routes). Containers could live under their own
EW> subdirectory (eg. /sys/containers/<id>/).
Well, that's a bit of extra work. IIRC, the multiple routing table
implementations converge at about the RTNL layer, making it rather
difficult to expose them via another interface.
Regardless, it wouldn't change this patch set but by a couple of
lines.
--
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
prev parent reply other threads:[~2010-05-29 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 14:42 [RFC] user-cr: Routing information in userspace Dan Smith
[not found] ` <1274884956-21005-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-05-26 14:42 ` [PATCH 1/3] [RFC] user-cr: Add a basic hooks system Dan Smith
2010-05-26 14:42 ` [PATCH 2/3] Make extract_headers.sh bring out the __NR_setns symbol Dan Smith
[not found] ` <1274884956-21005-3-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-06-15 14:30 ` Oren Laadan
2010-05-26 14:42 ` [PATCH 3/3] [RFC] user-cr: Hook implementation for userspace network bits Dan Smith
2010-05-29 3:13 ` [Devel] [RFC] user-cr: Routing information in userspace Enrico Weigelt
[not found] ` <20100529031349.GA10541-q9I3ByPDOfiE+EvaaNYduQ@public.gmane.org>
2010-05-29 18:09 ` Dan Smith [this message]
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=87r5kua8ba.fsf@caffeine.danplanet.com \
--to=danms-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=weigelt-EU+a56NjgY8@public.gmane.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.