Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Dec 2008 11:39:53 -0800
From:      Alfred Perlstein <alfred@freebsd.org>
To:        Joe Marcus Clarke <marcus@FreeBSD.org>
Cc:        Ed Schouten <ed@80386.nl>, arch@FreeBSD.org
Subject:   Re: RFC: New VOP to translate vnode to its component name
Message-ID:  <20081207193953.GJ27096@elvis.mu.org>
In-Reply-To: <1228670197.69753.24.camel@shumai.marcuscom.com>
References:  <1228667168.69753.16.camel@shumai.marcuscom.com> <20081207170354.GI18652@hoeg.nl> <1228670197.69753.24.camel@shumai.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
* Joe Marcus Clarke <marcus@FreeBSD.org> [081207 09:17] wrote:
> On Sun, 2008-12-07 at 18:03 +0100, Ed Schouten wrote:
> > Hello Joe,
> > 
> > * Joe Marcus Clarke <marcus@FreeBSD.org> wrote:
> > > Here is a patch to HEAD, along with a man page, for VOP_CNP.
> > 
> > Maybe this should be called VOP_COMPONENTNAME? I know, it's not as short
> > as VOP_CNP, but is probably less cryptic to people who are trying to
> > figure out how the VFS works.
> 
> I'm open to a new name, but VOP_COMPONENTNAME does seem a bit unwieldy.
> What about VOP_VPTONAME (in the same vein as VOP_VPTOFH)?

either VOP_VPTONAME or VOP_VPTOCNP

(this is cool)

-Alfred



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081207193953.GJ27096>