From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Juan J. Quintela" <quintela@fi.udc.es>
Cc: Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-mm@kvack.org
Subject: Re: 2.4 / 2.5 VM plans
Date: Thu, 29 Jun 2000 14:45:57 +0100 [thread overview]
Message-ID: <20000629144557.S3473@redhat.com> (raw)
In-Reply-To: <yttitutwlmi.fsf@serpe.mitica>; from quintela@fi.udc.es on Wed, Jun 28, 2000 at 11:17:57PM +0200
Hi,
On Wed, Jun 28, 2000 at 11:17:57PM +0200, Juan J. Quintela wrote:
> 2.5:
>
> 7) Make a ->flush method in the address_space operations
OK
> 8) This one is related with the FS, not MM specific, but FS people
> want to be able to allocate MultiPage buffers (see pagebuf from
> XFS) and people want similar functionality for other things.
Yes, but this should be layered on top of the page handling ---
there's no need to integrate it into the low levels of the page cache.
> 9) We need also to implement write clustering for fs/page cache/swap.
Same as above. When the pagebuf layer or whatever gets a write
request for a given page, it is perfectly at liberty to write out
adjacent pages too if it wants to. The VM doesn't have to enforce
that itself.
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/
next prev parent reply other threads:[~2000-06-29 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-25 3:51 2.4 / 2.5 VM plans Rik van Riel
2000-06-28 17:45 ` vii
2000-06-28 21:04 ` Juan J. Quintela
2000-06-28 21:17 ` Juan J. Quintela
2000-06-29 13:45 ` Stephen C. Tweedie [this message]
2000-06-29 13:44 ` Stephen C. Tweedie
2000-07-06 7:51 ` page_table_lock problem [was: Re: 2.4 / 2.5 VM plans] Andrey Savochkin
2000-07-06 13:32 ` Stephen C. Tweedie
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=20000629144557.S3473@redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=quintela@fi.udc.es \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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.