From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: Re: [RFD] L2 Network namespace infrastructure Date: Sat, 23 Jun 2007 08:20:40 -0700 Message-ID: <467D3A48.20706@candelatech.com> References: <467CF8AC.80103@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: "Eric W. Biederman" , netdev@vger.kernel.org, David Miller , jamal , Stephen Hemminger , Jeff Garzik , YOSHIFUJI Hideaki , Linux Containers To: Patrick McHardy Return-path: Received: from ns2.lanforge.com ([66.165.47.211]:54953 "EHLO ns2.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752442AbXFWPZx (ORCPT ); Sat, 23 Jun 2007 11:25:53 -0400 In-Reply-To: <467CF8AC.80103@trash.net> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Patrick McHardy wrote: > Eric W. Biederman wrote: > >> -- The basic design >> >> There will be a network namespace structure that holds the global >> variables for a network namespace, making those global variables >> per network namespace. >> >> One of those per network namespace global variables will be the >> loopback device. Which means the network namespace a packet resides >> in can be found simply by examining the network device or the socket >> the packet is traversing. >> >> Either a pointer to this global structure will be passed into >> the functions that need to reference per network namespace variables >> or a structure that is already passed in (such as the network device) >> will be modified to contain a pointer to the network namespace >> structure. >> > > > I believe OpenVZ stores the current namespace somewhere global, > which avoids passing the namespace around. Couldn't you do this > as well? > Will we be able to have a single application be in multiple name-spaces? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com