From: Greg Banks <gnb@melbourne.sgi.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: [PATCH] 1/3 - RPC metrics support
Date: Sun, 04 Apr 2004 16:17:19 +1000 [thread overview]
Message-ID: <406FA86F.A9748FFC@melbourne.sgi.com> (raw)
In-Reply-To: 482A3FA0050D21419C269D13989C611302B07BFD@lavender-fe.eng.netapp.com
"Lever, Charles" wrote:
>
> > Why not just save a copy of @devname in nfs_get_sb() ? It's
> > the same name that's stored in struct vfsmount and reported
> > in /proc/mounts.
>
> unless i've missed something, there are only two NFS functions
> that take vfsmount as an argument. one is nfs_show_options, and
> the other is nfs_getattr.
>
> the vfsmount struct is not available to the NFS client during a
> mount operation.
The devname string that fs/super.c:do_kern_mount() passes to
nfs_get_sb() via file_system_type->get_sb is passed to
alloc_vfsmount() and used there to initialise the vfsmount's
mnt_devname. So while NFS doesn't have the vfsmount it does
have the same devname string.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-04-04 6:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 2:35 [PATCH] 1/3 - RPC metrics support Lever, Charles
2004-04-04 6:17 ` Greg Banks [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 17:05 Lever, Charles
2004-04-02 0:17 ` Greg Banks
2004-04-02 0:36 ` Trond Myklebust
2004-04-02 0:49 ` Greg Banks
2004-04-02 1:41 ` Trond Myklebust
2004-04-02 2:42 ` Greg Banks
2004-04-01 16:45 Lever, Charles
2004-04-02 0:10 ` Greg Banks
2004-04-01 15:15 Lever, Charles
2004-04-01 23:58 ` Greg Banks
2004-04-02 0:34 ` Trond Myklebust
2004-04-02 2:33 ` Greg Banks
2004-03-31 16:57 Lever, Charles
2004-03-31 17:19 ` Trond Myklebust
2004-03-31 16:34 Lever, Charles
2004-03-31 16:46 ` Trond Myklebust
2004-04-01 8:13 ` Greg Banks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=406FA86F.A9748FFC@melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.