From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: dzafman@kahuna.cag.cpqcorp.net, linux-kernel@vger.kernel.org,
Alexander Viro <viro@math.psu.edu>
Subject: Re: NFS client llseek
Date: Mon, 17 Dec 2001 13:18:29 -0500 [thread overview]
Message-ID: <20011217181748.GA15970@cs.cmu.edu> (raw)
In-Reply-To: <200112140057.fBE0vDm05648@kahuna.cag.cpqcorp.net> <15385.62936.632242.570507@charged.uio.no>
In-Reply-To: <15385.62936.632242.570507@charged.uio.no>
On Fri, Dec 14, 2001 at 01:51:36PM +0100, Trond Myklebust wrote:
> Just one comment: Isn't it easier to do this in generic_file_llseek()
> itself using inode->i_op->revalidate()? That would make it work for
> coda and smbfs too...
Actually, as far as Coda is concerned this only adds overhead. Coda uses
AFS2 session semantics instead of UNIX semantics, so updates are only
propagated when a file is closed.
Adding this to the generic_file_llseek will force an useless but
expensive upcall (and RPC call to the server) to every seek to check for
an updated i_size while we already know that the i_size of the file
won't have to change until it is closed and reopened.
I guess we're just (mis-)using the revalidate call as a replacement of a
missing call to i_ops->getattr from sys_stat. So perhaps adding the
revalidate to the generic_llseek is fine, but I'll just have to get that
missing getattr call into the tree.
Jan
next prev parent reply other threads:[~2001-12-17 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 0:51 NFS client llseek dzafman
2001-12-14 12:42 ` Trond Myklebust
2001-12-14 12:51 ` Trond Myklebust
2001-12-17 18:18 ` Jan Harkes [this message]
2001-12-17 18:42 ` Alexander Viro
2001-12-17 20:34 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2001-12-14 20:45 dzafman
2001-12-14 23:13 ` Pedro M. Rodrigues
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=20011217181748.GA15970@cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=dzafman@kahuna.cag.cpqcorp.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@math.psu.edu \
/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.