From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: 2.3.32-pre4/SMP still doesn't boot on Compaq Proliant 1600
Date: Tue, 14 Dec 1999 17:41:42 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.991214171649.16967A-100000@kanga.kvack.org> (raw)
In-Reply-To: <Pine.GSO.4.10.9912141410220.16347-100000@weyl.math.psu.edu>
On Tue, 14 Dec 1999, Alexander Viro wrote:
> On Tue, 14 Dec 1999, Linus Torvalds wrote:
...
> > Sounds like a capital idea. Mind doing the block device pagecache first,
> > though, if you're already looking at this area?
>
> Frankly, I'ld rather start with massaging bmap() out of existence. I will
> do block device pagecache, all right, but there is one funny detail - we
> have serious code duplication between loopback and swap.
Ah, I see what you're talking about. In theory we make rw_swap_page use
the page cache operations of the filesystem (or block device) by simply
relabelling the page from its swap cache entry. Actually, if we use the
page cache for block device access, doesn't that mean that we can get rid
of the swapper_inode completely? This seems like an obvious way of doing
things, and unless people point out something that I'm missing entirely
here... It'll mean that brw_page goes away and is replaced by the use of
i_ops->readpage. That's seems good =)
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next parent reply other threads:[~1999-12-14 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.10.9912141410220.16347-100000@weyl.math.psu.edu>
1999-12-14 22:41 ` Benjamin C.R. LaHaise [this message]
1999-12-27 15:58 ` Andrea Arcangeli
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=Pine.LNX.3.96.991214171649.16967A-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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