From: ebiederm@xmission.com (Eric W. Biederman)
To: Chris Wedgwood <cw@f00f.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
viro@math.psu.edu, linux-mm@kvack.org
Subject: Re: RFC: Remove swap file support
Date: 14 Jul 2001 11:35:52 -0600 [thread overview]
Message-ID: <m13d7z4dmv.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20010715032528.E6722@weta.f00f.org>
Chris Wedgwood <cw@f00f.org> writes:
> On Sat, Jul 14, 2001 at 12:07:38AM -0600, Eric W. Biederman wrote:
>
> Yes, and no. I'd say what we need to do is update rw_swap_page to
> use the address space functions directly. With block devices and
> files going through the page cache in 2.5 that should remove any
> special cases cleanly.
>
> Will block devices go through the page cache in 2.5.x?
>
> I had hoped they would, that any block devices would just be
> page-cache views of underlying character devices, thus allowing us to
> remove the buffer-cache and the /dev/raw stuff.
<orcale>
Block devices will go through the page cache in 2.5. It will take a
while for the buffer cache to go away completely, but it is there for
the code paths that haven't been updated. Buffer heads will stay.
The /dev/raw stuff is for those users that don't want to the kernel to
cache their data and will continue to exist in some form.
</oracle>
I can't see how any device that doesn't support read or writing just a
byte can be a character device.
Eric
--
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-mm.org/
next prev parent reply other threads:[~2001-07-14 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B472C06.78A9530C@mandrakesoft.com>
2001-07-14 6:07 ` Eric W. Biederman
2001-07-14 15:25 ` Chris Wedgwood
2001-07-14 17:35 ` Eric W. Biederman [this message]
2001-07-15 3:42 ` Chris Wedgwood
2001-07-17 11:59 ` Chris Wedgwood
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=m13d7z4dmv.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=cw@f00f.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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