From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: sched-idle and disk-priorities for 2.6.X
Date: 26 Jan 2004 23:08:47 GMT [thread overview]
Message-ID: <bv46lv$6pu$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20040123210449.GA250@elf.ucw.cz
In article <20040123210449.GA250@elf.ucw.cz>,
Pavel Machek <pavel@ucw.cz> wrote:
| > > I'm afraid it needs to be more aggressive.
| >
| > OK, is the patch below any better ?
|
| Yes, this one actually works. When I launched two 150MB tasks, one of
| them with ulimit -m 1, the limited task yielded its memory to
| unlimited one. It worked as expected.
I'm not sure what "as expected" means with this small a limit, hopefully
not "pages its butt off." I am printing a hardcopy of the 2nd patch and
a bit of the surrounding code, and also compiling a new kernel with the
patch in place, so I can play a bit in the morning.
I also wonder if a sanity check is desirable on the minimum size. At
some point I would think the system would get a lot of overhead trying
to actually use a single 1k page :-(
Thanks for this prompt implementation, I do have a few applications
which can use it!
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2004-01-26 23:09 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
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 [this message]
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='bv46lv$6pu$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