From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Limiting program swap
Date: Wed, 08 Dec 2004 14:07:36 -0500 [thread overview]
Message-ID: <cp7iqj$57n$1@gatekeeper.tmr.com> (raw)
I have several machine of various memory sizes which suffer from really
poor performance when doing backups. This appears to be because all the
programs other than the backup quickly get swapped to make room for i/o
buffers.
Is there some standard portable way to prevent this, either by reserving
some memory for programs which will not get swapped regardless of i/o
pressure, or alternatively limiting the total memory used for i/o
buffers, dcache, and similar things?
I did a crude hack for 2.4.17, but if I'm missing some obvious trick I'd
rather not do something which can't go in the mainline kernel. Anyone
care to show me what I missed, or is this just a characteristic of Linux?
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next reply other threads:[~2004-12-08 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 19:07 Bill Davidsen [this message]
2004-12-08 19:14 ` Limiting program swap Marc-Christian Petersen
2004-12-08 19:35 ` William Lee Irwin III
2004-12-08 20:45 ` Jesper Juhl
2004-12-08 23:12 ` Con Kolivas
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='cp7iqj$57n$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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