From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH 2/2] mlock use lru_add_drain_all_async()
Date: Wed, 7 Oct 2009 12:37:41 +0900 [thread overview]
Message-ID: <2f11576a0910062037r785da04bg5723a1779f40d45c@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0910061226300.18309@gentwo.org>
2009/10/7 Christoph Lameter <cl@linux-foundation.org>:
> On Tue, 6 Oct 2009, KOSAKI Motohiro wrote:
>
>> Suppose you have 2 cpus, cpu1 is busy doing a SCHED_FIFO-99 while(1),
>> cpu0 does mlock()->lru_add_drain_all(), which does
>> schedule_on_each_cpu(), which then waits for all cpus to complete the
>> work. Except that cpu1, which is busy with the RT task, will never run
>> keventd until the RT load goes away.
>>
>> This is not so much an actual deadlock as a serious starvation case.
>>
>> Actually, mlock() doesn't need to wait to finish lru_add_drain_all().
>> Thus, this patch replace it with lru_add_drain_all_async().
>
> Ok so this will queue up lots of events for the cpu doing a RT task. If
> the RT task is continuous then they will be queued there forever?
Yes. this patch solved very specific issue only.
In original bug-report case, the system has two cpuset and the RT task
own one cpuset as monopoly. Thus, your worried thing doesn't occur.
Perhaps, we need complete solution. but I don't think this patch have
bad side effect. then, I hope to push it into mainline.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-10-07 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 2:40 [PATCH 1/2] Implement lru_add_drain_all_async() KOSAKI Motohiro
2009-10-06 2:41 ` [PATCH 2/2] mlock use lru_add_drain_all_async() KOSAKI Motohiro
2009-10-06 9:08 ` Peter Zijlstra
2009-10-06 10:11 ` KOSAKI Motohiro
2009-10-06 16:27 ` Christoph Lameter
2009-10-07 3:37 ` KOSAKI Motohiro [this message]
2009-10-06 22:59 ` Ying Han
2009-10-07 3:48 ` KOSAKI Motohiro
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=2f11576a0910062037r785da04bg5723a1779f40d45c@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@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