From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH 1/12] L2 network namespace (v3): current network namespace operations Date: Wed, 17 Jan 2007 13:16:02 -0700 Message-ID: References: <200701171851.14734.dim@openvz.org> <200701171857.40349.dim@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: containers@lists.osdl.org, alexey@sw.ru, netdev@vger.kernel.org, saw@sw.ru Return-path: Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:40833 "EHLO ebiederm.dsl.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932729AbXAQURE (ORCPT ); Wed, 17 Jan 2007 15:17:04 -0500 To: Dmitry Mishin In-Reply-To: <200701171857.40349.dim@openvz.org> (Dmitry Mishin's message of "Wed, 17 Jan 2007 18:57:40 +0300") Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Dmitry Mishin writes: > Added functions and macros required to operate with network namespaces. > They are required in order to switch network namespace for incoming packets and > to not extend current network interface by additional network namespace argue. Is exec_net only used in interrupt context? Or how do you ensure a sleeping function does not get called and the kernel process comes back on another cpu? Eric