linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Daniel Drake <ddrake@brontes3d.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: speeding up swapoff
Date: Thu, 30 Aug 2007 11:36:36 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708301132470.26365@blonde.wat.veritas.com> (raw)
In-Reply-To: <m1d4x52zri.fsf@ebiederm.dsl.xmission.com>

On Thu, 30 Aug 2007, Eric W. Biederman wrote:
> 
> There is one other possibility.  Typically the swap code is using
> compatibility disk I/O functions instead of the best the kernel
> can offer.  I haven't looked recently but it might be worth just
> making certain that there isn't some low-level optimization or
> cleanup possible on that path.  Although I may just be thinking
> of swapfiles.

Andrew rewrote swapfile support in 2.5, making it use FIBMAP at
swapon time: so that in 2.6 swapfiles are as deadlock-free and
as efficient (unless the swapfile happens to be badly fragmented)
as raw disk partitions.

There's certainly scope for a study of I/O patterns in swapping,
it's hard to imagine that improvements couldn't be made (but also
easy to imagine endless disputes over different kinds of workload).
But most people would appreciate an improvement in active swapping,
and not care very much about the swapoff.

Regarding Daniel's use of swapoff: it's a very heavy sledgehammer
for cracking that nut, I strongly agree with those who have pointed
him to mlock and mlockall instead.

Hugh

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-08-30 10:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 13:29 Daniel Drake
2007-08-29 14:30 ` Arjan van de Ven
2007-08-29 14:36   ` Oliver Neukum
2007-08-29 16:04     ` Hugh Dickins
2007-08-29 16:18       ` Oliver Neukum
2007-08-29 14:44   ` Daniel Drake
2007-08-29 15:12     ` Juergen Beisert
2007-08-30 15:57     ` Bill Davidsen
2007-09-01 22:20     ` Andi Kleen
2007-08-29 15:58   ` Hugh Dickins
2007-08-29 15:36 ` Hugh Dickins
2007-08-30  8:27   ` Eric W. Biederman
2007-08-30 10:36     ` Hugh Dickins [this message]
2007-08-30 15:05       ` Daniel Drake
2007-08-29 16:08 ` Lee Schermerhorn
     [not found] <fa.j/pO3mTWDugTdvZ3XNr9XpvgzPQ@ifi.uio.no>
     [not found] ` <fa.ed9fasZXOwVCrbffkPQTX7G3a7g@ifi.uio.no>
     [not found]   ` <fa./NZA3biuO1+qW5pW8ybdZMDWcZs@ifi.uio.no>
2007-08-30  1:37     ` Robert Hancock
2007-08-30 13:55       ` Helge Hafting
2007-08-30 14:06         ` Xavier Bestel
2007-08-30 14:06           ` Helge Hafting
2007-08-30 14:14             ` Xavier Bestel

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.4.64.0708301132470.26365@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=ddrake@brontes3d.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.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