From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org
Subject: question on comment in __oom_kill_task()
Date: Mon, 02 Apr 2007 11:45:46 -0600 [thread overview]
Message-ID: <4611414A.3050606@nortel.com> (raw)
In __oom_kill_task(), there is a comment that says,
"We give our sacrificial lamb high priority and access to all the memory
it needs. That way it should be able to exit() and clear out its
resources quickly..."
However, we don't actually change the priority at that point, we just
give it a large timeslice.
Would it make sense to actually change the priority/policy using
sched_setscheduler() to give the process a deeply negative nice level or
maybe even make it realtime?
This seems to help on some of our OOM stress tests.
Chris
reply other threads:[~2007-04-02 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4611414A.3050606@nortel.com \
--to=cfriesen@nortel.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 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.