linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Chuck Lever <cel@monkey.org>
Cc: linux-mm@kvack.org
Subject: Re: possible brw_page optimization
Date: Wed, 26 Jan 2000 13:01:16 +0000 (GMT)	[thread overview]
Message-ID: <14478.61468.943623.938788@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.BSO.4.10.10001211508270.26216-100000@funky.monkey.org>

Hi,

On Fri, 21 Jan 2000 15:21:33 -0500 (EST), Chuck Lever <cel@monkey.org>
said:

> i've been exploring swap compaction and encryption, and found that
> brw_page wants to break pages into buffer-sized pieces in order to
> schedule I/O.  

brw_page is there explicitly to perform physical block IO to disk.  If
you want to do compression or encription, I'd have thought you want to
do that at a higher level.  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.

--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/

  reply	other threads:[~2000-01-26 13:01 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 [this message]
2000-01-26 16:02   ` Chuck Lever
2000-01-26 23:24     ` Stephen C. Tweedie
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=14478.61468.943623.938788@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