From: Andi Kleen <andi@firstfloor.org>
To: Daniel Drake <ddrake@brontes3d.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: speeding up swapoff
Date: 02 Sep 2007 00:20:22 +0200 [thread overview]
Message-ID: <p73fy1yvxi1.fsf@bingen.suse.de> (raw)
In-Reply-To: <1188398683.22156.77.camel@localhost>
Daniel Drake <ddrake@brontes3d.com> writes:
>
> It's more-or-less a real life problem. We have an interactive
> application which, when triggered by the user, performs rendering tasks
> which must operate in real-time. In attempt to secure performance, we
> want to ensure everything is memory resident and that nothing might be
> swapped out during the process. So, we run swapoff at that time.
If the system gets under serious memory pressure it'll happily discard
your text pages too (and later reload them from disk). The same
for any file data you might need to access.
swapoff will only affect anonymous memory, but not all the other
memory you'll need as well.
There's no way around mlock/mlockall() to really prevent this.
Still even with that you could still lose dentries/inodes etc which
can also cause stalls. The only way to keep them locked
is to keep the files always open.
-Andi
--
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>
next prev parent reply other threads:[~2007-09-01 22:20 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 [this message]
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
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=p73fy1yvxi1.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=ddrake@brontes3d.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