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: Mon, 19 Jan 2004 16:39:59 +1100 [thread overview]
Message-ID: <400B6DAF.7090802@cyberone.com.au> (raw)
In-Reply-To: <400B621D.7050307@tmr.com>
Bill Davidsen wrote:
> Nick Piggin wrote:
>
>>
>>
>> Bill Davidsen wrote:
>>
>>>
>>> Or you could use "ulimit -m" to set the RSS, of course.
>>
>>
>>
>>
>> I don't think that would do anything with 2.6 :P
>
>
> Does that imply that the feature doesn't function as documented in
> 2.6? Or is that a SysV-ism not in SuS and documented but not
> implemented, or what other reason would there be for it to not work?
>
The first one. AFAIKS ulimit RSS doesn't do anything in the 2.6 vm.
Rik has a fairly straightforward looking implementation in his 2.4 vm
which probably wouldn't be too hard to forward port. It doesn't impose
a hard limit on RSS though: I'm not sure what the standards say about that.
next prev parent reply other threads:[~2004-01-19 5:40 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 [this message]
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=400B6DAF.7090802@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.