From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: Fix knfsd readahead cache in 2.4.15
Date: 27 Nov 2001 08:16:03 +0100 [thread overview]
Message-ID: <p73r8qksmz0.fsf@amdsim2.suse.de> (raw)
In-Reply-To: <15362.18626.303009.379772@charged.uio.no.suse.lists.linux.kernel> <15362.53694.192797.275363@esther.cse.unsw.edu.au.suse.lists.linux.kernel> <20011126.155347.45872112.davem@redhat.com.suse.lists.linux.kernel>
In-Reply-To: "David S. Miller"'s message of "27 Nov 2001 00:58:40 +0100"
"David S. Miller" <davem@redhat.com> writes:
>
> There are other problems remaining, this function is a logical
> mess.
It is also broken by design. It forces file systems that need more
state to maintain read/write ahead to maintain their own cache (e.g. XFS
which needs to cache extent allocations)
Better would be to just fix nfsd to cache open file handles, then all
this mess would be done by the VFS. In addition it would be faster
because it wouldn't need to execute an "open()" for every rpc operation.
-Andi
next parent reply other threads:[~2001-11-27 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15362.18626.303009.379772@charged.uio.no.suse.lists.linux.kernel>
[not found] ` <15362.53694.192797.275363@esther.cse.unsw.edu.au.suse.lists.linux.kernel>
[not found] ` <20011126.155347.45872112.davem@redhat.com.suse.lists.linux.kernel>
2001-11-27 7:16 ` Andi Kleen [this message]
2001-11-26 13:50 Trond Myklebust
2001-11-26 23:35 ` Neil Brown
2001-11-27 0:05 ` David S. Miller
2001-11-26 23:53 ` David S. Miller
2001-11-27 0:29 ` Neil Brown
2001-11-27 0:33 ` David S. Miller
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=p73r8qksmz0.fsf@amdsim2.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
all inboxes | Powered by JetHome®