From: Nick Piggin <piggin@cyberone.com.au>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Valdis.Kletnieks@vt.edu, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sched-idle and disk-priorities for 2.6.X
Date: Sun, 18 Jan 2004 02:29:37 +1100 [thread overview]
Message-ID: <400954E1.2050807@cyberone.com.au> (raw)
In-Reply-To: <400953B9.3090900@tmr.com>
Bill Davidsen wrote:
> Valdis.Kletnieks@vt.edu wrote:
>
>> A better bet would be a patch that allowed you to set the maximum RSS
>> size for
>> the process so it can basically thrash itself while leaving enough
>> memory for
>> everybody else (and yes, I *know* how this can be self-defeating if the
>> thrashing app then increases the total I/O consumed to be higher than
>> the I/O
>> bandwidth available - the point is that it's probably the high RSS
>> value for
>> his application causing OTHER things to thrash that's the root cause
>> of his
>> performance problem).
>
>
> Or you could use "ulimit -m" to set the RSS, of course.
I don't think that would do anything with 2.6 :P
next prev parent reply other threads:[~2004-01-17 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 18:10 sched-idle and disk-priorities for 2.6.X Pavel Machek
2004-01-16 19:37 ` Valdis.Kletnieks
2004-01-17 15:24 ` Bill Davidsen
2004-01-17 15:29 ` Nick Piggin [this message]
2004-01-19 4:50 ` Bill Davidsen
2004-01-19 5:39 ` Nick Piggin
2004-01-17 23:29 ` Pavel Machek
2004-01-18 18:47 ` Rik van Riel
2004-01-18 19:58 ` Pavel Machek
2004-01-21 19:49 ` Rik van Riel
2004-01-22 1:04 ` Pavel Machek
2004-01-22 1:13 ` Rik van Riel
2004-01-23 18:59 ` Pavel Machek
2004-01-23 19:04 ` Rik van Riel
2004-01-23 21:04 ` Pavel Machek
2004-01-26 23:08 ` bill davidsen
2004-02-03 19:13 ` Pavel Machek
2004-01-26 2:06 ` Bill Davidsen
2004-01-26 7:19 ` Pavel Machek
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=400954E1.2050807@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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