From: ebiederm@xmission.com (Eric W. Biederman)
To: Marek Kierdelewicz <marek@piasta.pl>
Cc: containers@lists.linux-foundation.org, netfilter@vger.kernel.org
Subject: Re: lxc, conntrack and routecache
Date: Tue, 06 Apr 2010 08:05:42 -0700 [thread overview]
Message-ID: <m1iq84aaex.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20100404090757.6f1ac500@catlap> (Marek Kierdelewicz's message of "Sun\, 4 Apr 2010 09\:07\:57 +0200")
Marek Kierdelewicz <marek@piasta.pl> writes:
> 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?
What does it matter?
Eric
prev parent reply other threads:[~2010-04-06 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 7:07 lxc, conntrack and routecache Marek Kierdelewicz
2010-04-06 15:05 ` Eric W. Biederman [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=m1iq84aaex.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=containers@lists.linux-foundation.org \
--cc=marek@piasta.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox