[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D22362F.2040604@parallels.com>
Date: Mon, 3 Jan 2011 14:48:47 -0600
From: Rob Landley <rlandley@...allels.com>
To: Trond Myklebust <Trond.Myklebust@...app.com>
CC: "Kirill A. Shutemov" <kas@...nvz.org>,
Rob Landley <rob@...dley.net>,
"J. Bruce Fields" <bfields@...ldses.org>,
Neil Brown <neilb@...e.de>,
Pavel Emelyanov <xemul@...allels.com>,
<linux-nfs@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 00/12] make rpc_pipefs be mountable multiple time
On 12/31/2010 10:54 AM, Trond Myklebust wrote:
>> I'm kind of surprised that the kernel cares about a specific path under
>> /var/lib. (Seems like policy in the kernel somehow.) Can't it just
>> check the current process's mount list to see if an instance of
>> rpc_pipefs is mounted in the current namespace the way lxc looks for
>> cgroups? Or are there potential performance/scalability issues with that?
>
> The kernel doesn't give a damn about the /var/lib/nfs/rpc_pipefs bit.
> That's all for the benefit of the userland utilities.
Are you saying that if you go into a container and that mount point
doesn't exist, the kernel will still be able to find and use rpc_pipefs?
Without userspace creating a specific magic path and mounting a
filesystem on it?
If so, I misread the patch...
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists