From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: riel@conectiva.com.br
Cc: linux-mm@kvack.org
Subject: Write-back/VM question
Date: Mon, 09 Oct 2000 16:09:40 -0700 [thread overview]
Message-ID: <39E25034.6B1203CE@sgi.com> (raw)
One of the behaviors of the new VM seems
to be that it starts I/O on a written page
fairly early. This "aggressive" write is
great for streaming I/O, but seems to have
a penalty when the application has write-locality.
Dbench is a one case, which is write intensive
and a lot of the writes are to a previously written page.
I'm not exactly certain why starting write-out
early would cause problems, but I've a couple of
quick questions:
1. Is the page locked during write-out?
2. Is there a tuneable that I can use to
control write-back behaviour?
thanks!
--
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
--
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/
next reply other threads:[~2000-10-09 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-09 23:09 Rajagopal Ananthanarayanan [this message]
2000-10-09 23:11 ` Write-back/VM question Rik van Riel
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=39E25034.6B1203CE@sgi.com \
--to=ananth@sgi.com \
--cc=linux-mm@kvack.org \
--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 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.