From: Christoph Hellwig <hch@caldera.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: MM/VM todo list
Date: Fri, 5 Jan 2001 22:34:59 +0100 [thread overview]
Message-ID: <20010105223459.A12653@caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0101051927040.1295-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Fri, Jan 05, 2001 at 07:27:38PM -0200
On Fri, Jan 05, 2001 at 07:27:38PM -0200, Rik van Riel wrote:
> > No other then filesystem IO (page/buffercache) is actively tied
> > to the VM, so there should be no problems.
>
> Not right now, no. But if you know what is possible
> (and planned) with the kiobuf layer, you should think
> twice about this idea...
I don't think so. The only place were IO actively interferes with
the VM is of the 'write this out when memory gets low' type thing,
and you don't really want this outside filesystems/blockdevices.
There are some VM tricks that are usefull for IO (COW, map_user_kiobuf),
but these operate always on pages (maybe containered by kiobufs, but that
should be of minor interest for the VM).
Christoph
--
Whip me. Beat me. Make me maintain AIX.
--
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 prev parent reply other threads:[~2001-01-05 21:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:14 Rik van Riel
2001-01-05 15:54 ` Marcelo Tosatti
2001-01-05 17:50 ` Rik van Riel
2001-01-05 16:56 ` Marcelo Tosatti
2001-01-05 21:13 ` Christoph Hellwig
2001-01-05 21:20 ` Rik van Riel
2001-01-05 21:26 ` Christoph Hellwig
2001-01-05 21:27 ` Rik van Riel
2001-01-05 21:34 ` Christoph Hellwig [this message]
2001-01-05 21:52 ` Stephen C. Tweedie
2001-01-05 17:58 ` Daniel Phillips
2001-01-08 17:31 ` afei
2001-01-08 17:36 ` Rik van Riel
2001-01-08 20:23 ` Rasmus Andersen
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=20010105223459.A12653@caldera.de \
--to=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--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