[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110725225154.GD22133@ZenIV.linux.org.uk>
Date: Mon, 25 Jul 2011 23:51:54 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Tim Chen <tim.c.chen@...ux.intel.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Andi Kleen <andi@...stfloor.org>,
Matthew Wilcox <matthew@....cx>,
Anton Blanchard <anton@...ba.org>, npiggin@...nel.dk,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [Patch] VFS : mount lock scalability for files systems without
mount point (WAS vfsmount lock issues on very large ppc64 box)
On Mon, Jul 25, 2011 at 03:39:10PM -0700, Tim Chen wrote:
> On Sat, 2011-07-23 at 09:24 -0400, Christoph Hellwig wrote:
> > I think you actually want this done in kern_mount_data, as both
> > ipc and proc want long-term references as well. I also suspect with
> > additional creep of container awareness more internal mounts will switch
> > to kern_mount_data. Al, what do you think about simply passing the
> > private data argument to kern_mount and kill kern_mount_data? It's not
> > like the additional argument is going to cause us any pain.
> >
> >
>
> I've updated the patch and merged mnt_make_longterm into
> kern_mount_data to address your comments. I've left the kern_mount
> and kern_mount_data as separate functions for now. Let me know
> if removing kern_mount_data is preferable instead.
It's mostly merged in mainline already... BTW, you forgot to export
that sucker - mtdchar can be modular.
--
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