From: Christoph Rohland <cr@sap.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: tmpfs swapoff oddity
Date: 08 Feb 2001 11:17:16 +0100 [thread overview]
Message-ID: <m366ilcwcz.fsf@linux.local> (raw)
In-Reply-To: <Pine.Linu.4.10.10102080953430.1381-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10102080953430.1381-100000@mikeg.weiden.de>
Hi Mike,
On Thu, 8 Feb 2001, Mike Galbraith wrote:
> Hi Christoph,
>
> While testing Jens' loop-4 patch (and not being able to find
> any way to lock it up), I stumbled onto a strange behavior.
>
> I set up an interleaved swap with one swap partition, and one
> swapfile in a loopback mounted reiserfs - populated tmpfs with
> a kernel tree and did hefty make -j kernel builds to generate
> much I/O. Afterward (bored), I figured I'd bounce the data in
> tmpfs back and forth between swap containers with swapoff. It
> took much longer than I expected.
Oh, the swapoff handling in Linux is much less then suboptimal. So I
would expect that.
To explain: For every single page on swap we scan all processes vmas
and all shm/tmpfs objects swap tables :-( And we have to hold some
locks for that...
Greetings
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-08 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 9:31 tmpfs swapoff oddity Mike Galbraith
2001-02-08 10:17 ` Christoph Rohland [this message]
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=m366ilcwcz.fsf@linux.local \
--to=cr@sap.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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