From: Marek Kierdelewicz <marek@piasta.pl>
To: containers@lists.linux-foundation.org, netfilter@vger.kernel.org
Subject: lxc, conntrack and routecache
Date: Sun, 4 Apr 2010 09:07:57 +0200 [thread overview]
Message-ID: <20100404090757.6f1ac500@catlap> (raw)
Hi,
I'm evaluating lxc for use in virtualized routing/bridgeing
infrastructure. I'm particulary interested in conntrack and routecache
behaviour. I had run some tests and established that routecache and
conntrack is not shared between containers and base system. Are data
structures for routeche and conntrack in kernel shared (with each entry
marked with namespace id) or new data structure is created for each new
container?
Spare me RTFS. Thx
Regards,
Marek
next reply other threads:[~2010-04-04 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 7:07 Marek Kierdelewicz [this message]
2010-04-06 15:05 ` lxc, conntrack and routecache Eric W. Biederman
[not found] ` <m1iq84aaex.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2010-04-06 15:43 ` Marek Kierdelewicz
2010-04-06 15:05 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2010-04-04 7:07 Marek Kierdelewicz
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=20100404090757.6f1ac500@catlap \
--to=marek@piasta.pl \
--cc=containers@lists.linux-foundation.org \
--cc=netfilter@vger.kernel.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.