From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: Device Namespaces Date: Wed, 02 Oct 2013 17:59:36 -0700 Message-ID: <87ioxff9tz.fsf@xmission.com> References: <87a9iri3ot.fsf@xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87a9iri3ot.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org> (Eric W. Biederman's message of "Wed, 02 Oct 2013 17:44:02 -0700") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Amir Goldstein Cc: Greg Kroah-Hartman , Linux Containers , Kay Sievers , Andy Lutomirski , devel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org, lxc-devel , mhw-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org, Stephane Graber List-Id: containers.vger.kernel.org ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) writes: >> This kind of API is a required building block for us to write device >> drivers that are namespace aware in a way that userspace will have >> enough flexibility for dynamic configuration. >> >> We are trying to come up with a proposal for that sort of API. When >> we have something decent, we shall post it. > > I really think what you need to write are special drivers that > facilitate your use case. Even more practically if you can write special drivers it removes a level of policy from the kernel, and allows those special drivers to use at other times for other occassions. Eric