From: Benjamin LaHaise <bcrl@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] Re: Fix knfsd readahead cache in 2.4.15
Date: Wed, 28 Nov 2001 16:03:06 -0500 [thread overview]
Message-ID: <20011128160306.F23086@redhat.com> (raw)
In-Reply-To: <15362.18626.303009.379772@charged.uio.no> <15362.53694.192797.275363@esther.cse.unsw.edu.au> <20011126.155347.45872112.davem@redhat.com> <20011126202509.J15582@redhat.com> <15363.39718.446155.619699@charged.uio.no> <20011127102348.A19330@redhat.com> <15363.46302.205479.958516@charged.uio.no>
In-Reply-To: <15363.46302.205479.958516@charged.uio.no>; from trond.myklebust@fys.uio.no on Tue, Nov 27, 2001 at 04:44:30PM +0100
On Tue, Nov 27, 2001 at 04:44:30PM +0100, Trond Myklebust wrote:
> Ah, OK. Sorry for being so dense ;-)
>
> Yeah, that would be an improvement for knfsd too. The current scheme
> can only manage readahead for 1 reader per inode.
> Are there any records of a more detailed discussion of how to go about
> implementing such a readahead strategy for Linux?
Not yet. I'm hoping to write such a patch in the next couple of months
for 2.5.
-ben
--
Fish.
prev parent reply other threads:[~2001-11-28 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 13:50 Fix knfsd readahead cache in 2.4.15 Trond Myklebust
2001-11-26 23:35 ` Neil Brown
2001-11-26 23:53 ` David S. Miller
2001-11-27 0:05 ` David S. Miller
2001-11-27 0:29 ` Neil Brown
2001-11-27 0:33 ` David S. Miller
2001-11-27 1:25 ` [NFS] " Benjamin LaHaise
2001-11-27 13:54 ` Trond Myklebust
2001-11-27 15:23 ` Benjamin LaHaise
2001-11-27 15:44 ` Trond Myklebust
2001-11-28 21:03 ` Benjamin LaHaise [this message]
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=20011128160306.F23086@redhat.com \
--to=bcrl@redhat.com \
--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 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.