From: Pavel Machek <pavel@ucw.cz>
To: Rik van Riel <riel@redhat.com>
Cc: Valdis.Kletnieks@vt.edu, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sched-idle and disk-priorities for 2.6.X
Date: Thu, 22 Jan 2004 02:04:38 +0100 [thread overview]
Message-ID: <20040122010438.GD223@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0401211448250.26332-100000@chimarrao.boston.redhat.com>
Hi!
> > > > Is there effective way to limit RSS?
> > >
> > > Want me to port the RSS stuff from 2.4-rmap to 2.6 ?
> >
> > Well, if it allows me to limit memory for one task so that it does not
> > make system unusable... yes, that would be great.
>
> Here it is. Untested, except for whether it compiles cleanly ;)
>
> Let me know how it works, if the enforcement is aggressive
> enough or not, whether I need to tweak things etc...
It boots, and seems to have no ill effects. I've yet to see some good
effects, too...
doing
ulimit -m 1
<some task>
should make that task run with extremely low priority, right?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-01-22 1:04 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
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 [this message]
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=20040122010438.GD223@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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