linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: 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 00:07:38 -0600	[thread overview]
Message-ID: <m1elrk3uxh.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3B472C06.78A9530C@mandrakesoft.com>

Jeff Garzik <jgarzik@mandrakesoft.com> writes:

> Since you can make any file into a block device using loop,
> is there any value to supporting swap files in 2.5?
> 
> swap files seem like a special case that is no longer necessary...

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.

In 2.4 the swap code really hasn't been updated, the old code has only
been patched enough to work on 2.4.  This adds layers of work that we
really don't need to be doing.  Removing the extra redirection has the
potential to give a small performance boost to swapping.

The case to watch out for are deadlocks doing things like using
swapfiles on an NFS mount.  As you point out we can already do this
with the loop back devices so it isn't really a special case.  The
only new case I can see working are swapfiles with holes in them, or
swapfiles that do automatic compression.  I doubt those cases are
significant improvements but it looks like they will fall out
naturally. 

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/

       reply	other threads:[~2001-07-14  6:07 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 [this message]
2001-07-14 15:25   ` Chris Wedgwood
2001-07-14 17:35     ` Eric W. Biederman
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=m1elrk3uxh.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --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