From: "Stephen C. Tweedie" <sct@redhat.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: nr_async_pages and swapin readahead on -ac series
Date: Fri, 9 Mar 2001 11:02:16 +0000 [thread overview]
Message-ID: <20010309110216.B11513@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103081944560.2336-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Thu, Mar 08, 2001 at 07:47:59PM -0300
Hi,
On Thu, Mar 08, 2001 at 07:47:59PM -0300, Marcelo Tosatti wrote:
>
> > Swapin is always synchronous: it happens in response to a task's page
> > fault. As such it is always going to be rate-limited automatically.
> > I don't think it's too important to count reads in nr_async_pages, nor
> > to throttle readaheads if nr_async_pages is too large.
>
> Its not really throttling. We just _bypass_ the readahead's in case we got
> too much.
I know, but I still think it's worth doing the readahead in any case.
We've got 8192 request slots per swap device so we're not going to
suddenly go synchronous because of readahead, and the callers are
naturally throttled (because they wait synchronously on the requested
page) so we don't have to worry about submitting unbounded IO.
An extra seek is _so_ much more expensive than the
readahead/readaround that I doubt it's worth making it conditional.
Cheers,
Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2001-03-09 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 1:57 Marcelo Tosatti
2001-03-08 12:17 ` Rik van Riel
2001-03-08 20:17 ` Stephen C. Tweedie
2001-03-08 22:47 ` Marcelo Tosatti
2001-03-09 11:02 ` Stephen C. Tweedie [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=20010309110216.B11513@redhat.com \
--to=sct@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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