All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xunlei Pang <xpang@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Juri Lelli <juri.lelli@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] sched/deadline: No need to check NULL later_mask
Date: Wed, 6 Apr 2016 21:08:02 +0800	[thread overview]
Message-ID: <57050A32.9000009@redhat.com> (raw)
In-Reply-To: <20160406093036.GQ3448@twins.programming.kicks-ass.net>

On 2016/04/06 at 17:30, Peter Zijlstra wrote:
> On Sat, Apr 02, 2016 at 06:14:28PM +0800, Xunlei Pang wrote:
>> Your proposal is very nice!
>>
>> At the sched_init() stage we only have one (to be "idle") task and with irq disabled,
>> no scheduling will happen, and the cpu_possible_mask was already initiated, so it's
>> safe to simply move them there.
>>
>> Also, how about rt&deadline sharing a percpu mask? Because only one of them can
>> use the mask at a moment, operations are always under some spin_lock_irqsave().
>>
>> I made a new patch below, slightly tested by running tens of rt&dl tasks for a while,
>> are you fine with it?
> Yep, looks fine. Please submit as a proper patch.

Will do, thanks!

Regards,
Xunlei

>
> Thanks!

      reply	other threads:[~2016-04-06 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 11:13 [PATCH] sched/deadline: No need to check NULL later_mask Xunlei Pang
2016-04-01 11:29 ` Peter Zijlstra
2016-04-01 12:16   ` Xunlei Pang
2016-04-01 16:21     ` Peter Zijlstra
2016-04-02 10:14       ` Xunlei Pang
2016-04-06  9:30         ` Peter Zijlstra
2016-04-06 13:08           ` Xunlei Pang [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=57050A32.9000009@redhat.com \
    --to=xpang@redhat.com \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=xlpang@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 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.