[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100226.040855.158431085.davem@davemloft.net>
Date: Fri, 26 Feb 2010 04:08:55 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: danms@...ibm.com
Cc: containers@...ts.osdl.org, benjamin.thery@...l.net, den@...nvz.org,
ebiederm@...ssion.com, netdev@...r.kernel.org
Subject: Re: [PATCH 2/6] C/R: Basic support for network namespaces and
devices (v5)
From: Dan Smith <danms@...ibm.com>
Date: Thu, 25 Feb 2010 12:43:11 -0800
> When checkpointing a task tree with network namespaces, we hook into
> do_checkpoint_ns() along with the others. Any devices in a given namespace
> are checkpointed (including their peer, in the case of veth) sequentially.
> Each network device stores a list of protocol addresses, as well as other
> information, such as hardware address.
>
> This patch supports veth pairs, as well as the loopback adapter. The
> loopback support is there to make sure that any additional addresses and
> state (such as up/down) is copied to the loopback adapter that we are
> given in the new network namespace.
>
> On restart, we instantiate new network namespaces and veth pairs as
> necessary. Any device we encounter that isn't in a network namespace
> that was checkpointed as part of a task is left in the namespace of the
> restarting process. This will be the case for a veth half that exists
> in the init netns to provide network access to a container.
To be safe you should probably use __be32 and store the IP
addresses in network byte order.
But other than that:
Acked-by: David S. Miller <davem@...emloft.net>
--
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