From: Honghui Zhang <zhanghonghui@huawei.com>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: Steven Rostedt <rostedt@goodmis.org>,
<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] sched/rt: Decrease number of calls of push_rt_task() in push_rt_tasks()
Date: Tue, 5 Feb 2013 16:25:11 +0800 [thread overview]
Message-ID: <5110C1E7.9020106@huawei.com> (raw)
In-Reply-To: <500221360048944@web26g.yandex.ru>
On 2013/2/5 15:22, Kirill Tkhai wrote:
>>
>> Suppose we have a large number of cpus(say 4096), with the last one running
>> a low-priority task on it. Is it possible with this patch we will never reach
>> the last cpu in case that previous cpu has complete the pulled task?
>
> Yes. But this patch is about several pushable tasks on the same cpu.
>
> Kirill
>
Maybe I haven't make myself understood, but in that case, there will be a higher-priority
task in the runqueue of the pushing cpu, and a lower-priority task running in the last cpu
which could not be preempt by push_rt_task(), I don't think it's acceptable.
Hans
next prev parent reply other threads:[~2013-02-05 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 7:22 Re:[PATCH] sched/rt: Decrease number of calls of push_rt_task() in push_rt_tasks() Kirill Tkhai
2013-02-05 8:25 ` Honghui Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-27 23:46 [PATCH] " Kirill Tkhai
2013-01-31 16:08 ` Steven Rostedt
2013-01-31 21:57 ` Kirill Tkhai
2013-02-05 3:37 ` Honghui Zhang
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=5110C1E7.9020106@huawei.com \
--to=zhanghonghui@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tkhai@yandex.ru \
/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.