[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070912.025244.48515110.davem@davemloft.net>
Date: Wed, 12 Sep 2007 02:52:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ebiederm@...ssion.com
Cc: netdev@...r.kernel.org, containers@...ts.osdl.org
Subject: Re: [PATCH 03/16] net: Basic network namespace infrastructure.
From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Sat, 08 Sep 2007 15:15:34 -0600
>
> This is the basic infrastructure needed to support network
> namespaces. This infrastructure is:
> - Registration functions to support initializing per network
> namespace data when a network namespaces is created or destroyed.
>
> - struct net. The network namespace data structure.
> This structure will grow as variables are made per network
> namespace but this is the minimal starting point.
>
> - Functions to grab a reference to the network namespace.
> I provide both get/put functions that keep a network namespace
> from being freed. And hold/release functions serve as weak references
> and will warn if their count is not zero when the data structure
> is freed. Useful for dealing with more complicated data structures
> like the ipv4 route cache.
>
> - A list of all of the network namespaces so we can iterate over them.
>
> - A slab for the network namespace data structure allowing leaks
> to be spotted.
>
> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com>
I realize there are some discussions about naming and fixing
some races, but I applied this anyways so we can make some
forward progress.
We can make name changes and fixes on top of this initial work.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists