From: Kirill Tkhai <tkhai@yandex.ru>
To: Oleg Nesterov <oleg@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
LKML <linux-kernel@vger.kernel.org>, "lkp@01.org" <lkp@01.org>
Subject: Re: [sched] Out of memory: Kill process 2999 (rc) score 9 or sacrifice child
Date: Mon, 11 Aug 2014 10:11:33 +0400 [thread overview]
Message-ID: <3568281407737493@web29j.yandex.ru> (raw)
In-Reply-To: <20140810152914.GA11947@redhat.com>
10.08.2014, 19:31, "Oleg Nesterov" <oleg@redhat.com>:
> On 08/09, Peter Zijlstra wrote:
>> That would suggest we're failing to do the TASK_DEAD thing properly, and
>> ARGH! bloody obvious why, see the this_rq() comment right before the
>> finish_task_switch() call in context_switch().
>
> Off-topic, but perhaps we can make this a bit more clear?
>
> Hmm. But after I actually did this change I can't understand if it makes
> this more clean or uglifies the code. See the patch below.
>
> OTOH, "int cpu" in __schedule() looks pointless and should die? Both
> rcu_note_context_switch() and wq_worker_sleeping() can use
> raw_smp_processor_id() ? In fact I think wq_worker_sleeping() doesn't
> need the "task" argument too.
>
> And... Doesn't schedule_tail() need preempt_enable() before
> finish_task_switch() ? IOW, shouldn't it do
>
> #ifndef __ARCH_WANT_UNLOCKED_CTXSW
> preempt_disable();
> #endif
> finish_task_switch();
> post_schedule(rq);
>
> preempt_enable();
>
> or I am totally confused?
You're sure, this was discussed here:
https://lkml.org/lkml/2014/2/14/243
prev parent reply other threads:[~2014-08-11 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 14:30 [sched] Out of memory: Kill process 2999 (rc) score 9 or sacrifice child Fengguang Wu
2014-08-09 18:46 ` Peter Zijlstra
2014-08-09 19:24 ` Oleg Nesterov
2014-08-10 15:29 ` Oleg Nesterov
2014-08-11 6:11 ` Kirill Tkhai [this message]
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=3568281407737493@web29j.yandex.ru \
--to=tkhai@yandex.ru \
--cc=dave.hansen@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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