From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: A Question about the 2.4.21 Pathconf patch
Date: Tue, 29 Apr 2003 17:18:05 -0400 [thread overview]
Message-ID: <3EAEEC0D.6040006@RedHat.com> (raw)
In-Reply-To: shssms1ozz6.fsf@charged.uio.no
Trond Myklebust wrote:
> > So I'm just curious, why (from a protocol purest standpoint)
> > its not being used... and if it ever was used, what were the
> > results...
>
>I'm not sure I understand the question. In which case do you think we
>should be using FSINFO/STATFS (but are currently not doing so)?
>
In the linux-2.4.21-08-pathconf.dif patch, nfs_proc_fsinfo()
does a rpc_call(NFSPROC_STATFS) call and then fill in
the nfs_fsinfo structure with constants and values returned
in the nfs2_statfs structure.
I'm just wondering why nfs_proc_fsinfo() doesn't do a
rpc_call(NFSPROC_FSINFO) which would fill the nfs_fsinfo
structure with the values from the server. Of course these
values would have to be check for sanity... I just seems to
me that would be good information to to have on hand...
SteveD.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-29 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 15:08 A Question about the 2.4.21 Pathconf patch Steve Dickson
2003-04-29 16:22 ` Trond Myklebust
2003-04-29 18:41 ` Steve Dickson
2003-04-29 19:39 ` Trond Myklebust
2003-04-29 21:18 ` Steve Dickson [this message]
2003-04-29 22:47 ` Trond Myklebust
2003-04-30 2:14 ` Steve Dickson
2003-04-29 19:55 ` Trond Myklebust
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=3EAEEC0D.6040006@RedHat.com \
--to=steved@redhat.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.