From: "Stephen C. Tweedie" <sct@redhat.com>
To: Chuck Lever <cel@monkey.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: possible brw_page optimization
Date: Wed, 26 Jan 2000 23:24:11 +0000 (GMT) [thread overview]
Message-ID: <14479.33307.9093.845257@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.BSO.4.10.10001261054300.27169-100000@funky.monkey.org>
Hi,
On Wed, 26 Jan 2000 11:02:37 -0500 (EST), Chuck Lever <cel@monkey.org>
said:
> however, somehow i'd have to guarantee that all buffers associated with a
> page that is to be compressed/encrypted are read/written at once.
Why? The swapper already does per-page IO locking, so you are protected
against any conflicts while a page is being written out.
>> The clean way to do this would be to provide a virtual file to swap
>> over, and to allow rw_swap_page_base() to pass the page read or write
>> to that file's inode's read_/write_page methods. Then you can do any
>> munging you want on the virtual swap file without polluting the
>> underlying swap IO code.
> using a unique swap file/device makes it easy to tell when you need to
> decrypt a page. :)
Sure, but the inode already gives you such an abstraction --- why invent
a new one?
--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-01-26 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 20:21 Chuck Lever
2000-01-26 13:01 ` Stephen C. Tweedie
2000-01-26 16:02 ` Chuck Lever
2000-01-26 23:24 ` Stephen C. Tweedie [this message]
2000-01-27 18:50 ` Chuck Lever
2000-01-27 19:52 ` 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=14479.33307.9093.845257@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=cel@monkey.org \
--cc=linux-mm@kvack.org \
/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