From: "Stephen C. Tweedie" <sct@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Ext2 devel <ext2-devel@lists.sourceforge.net>,
NFS maillist <nfs@lists.sourceforge.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Re: [NFS] htree+NFS (NFS client bug?)
Date: Thu, 28 Nov 2002 16:41:43 +0000 [thread overview]
Message-ID: <20021128164143.D2362@redhat.com> (raw)
In-Reply-To: <shslm3e4or2.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Wed, Nov 27, 2002 at 11:44:01PM +0100
Hi,
On Wed, Nov 27, 2002 at 11:44:01PM +0100, Trond Myklebust wrote:
> We could possibly cache the EOF status by overloading some other field
> in the struct file. f_version comes to mind as a useful candidate,
> since it automatically gets reset by llseek.
If you want it to be preserved in cache, it needs to be in the inode,
not in the file.
--Stephen
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
next prev parent reply other threads:[~2002-11-28 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 23:44 htree+NFS (NFS client bug?) Jeremy Fitzhardinge
2002-11-27 3:26 ` [NFS] " Trond Myklebust
2002-11-27 2:59 ` [Ext2-devel] " chrisl
2002-11-27 8:58 ` Jeremy Fitzhardinge
2002-11-27 15:00 ` Stephen C. Tweedie
2002-11-27 20:25 ` [Ext2-devel] " Trond Myklebust
2002-11-27 20:55 ` Stephen C. Tweedie
2002-11-27 22:44 ` [Ext2-devel] " Trond Myklebust
2002-11-28 16:41 ` Stephen C. Tweedie [this message]
2002-11-28 16:58 ` Trond Myklebust
2002-11-28 17:09 ` Stephen C. Tweedie
2002-11-28 17:57 ` Trond Myklebust
2002-11-28 16:44 ` Stephen C. Tweedie
2002-11-28 17:13 ` Stephen C. Tweedie
2002-11-28 17:44 ` Trond Myklebust
2002-11-28 20:00 ` [Ext2-devel] " Jeremy Fitzhardinge
2002-11-28 2:07 ` Jeremy Fitzhardinge
2002-11-28 2:46 ` Trond Myklebust
2002-11-27 13:33 ` Theodore Ts'o
2002-11-27 20:42 ` 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=20021128164143.D2362@redhat.com \
--to=sct@redhat.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox