From: Andrew Morton <akpm@zip.com.au>
To: Urban Widmark <urban@teststation.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] smbfs async readpage
Date: Tue, 06 Aug 2002 21:57:56 -0700 [thread overview]
Message-ID: <3D50A8D4.AA31B1DD@zip.com.au> (raw)
In-Reply-To: Pine.LNX.4.44.0208070051220.8176-100000@cola.enlightnet.local
Urban Widmark wrote:
>
> This patch implements async readpage for smbfs. It seems to generate
> readahead judging from the network traffic and profile_readahead output
> from 2.4.
>
You'll find that each smbfs inode has its mapping->backing_dev_info
pointing at the global default_backing_dev_info. Which is not
tunable.
What you can do (please, I'd be interested in checking that it's
workable) is to create an smbfs_backing_dev_info, and arrange
(in smb_iget) for each new inode's mapping->backing_dev_info
to point at it.
Then implement some way of diddling smbfs_backing_dev_info.ra_pages
and voila, tunable readahead.
next prev parent reply other threads:[~2002-08-07 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 0:15 [PATCH] smbfs async readpage Urban Widmark
2002-08-07 4:57 ` Andrew Morton [this message]
2002-08-07 13:04 ` Urban Widmark
2002-08-07 17:34 ` Andrew Morton
2002-08-07 22:05 ` Urban Widmark
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=3D50A8D4.AA31B1DD@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-fsdevel@vger.kernel.org \
--cc=urban@teststation.com \
/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.