linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: cgel.zte@gmail.com
Cc: yzaikin@google.com, liu.hailong6@zte.com.cn, mingo@redhat.com,
	juri.lelli@redhat.com, vincent.guittot@linaro.org,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
	mcgrof@kernel.org, keescook@chromium.org, pjt@google.com,
	yang.yang29@zte.com.cn, joshdon@google.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Zeal Robot <zealci@zte.com.cm>
Subject: Re: [PATCH] sched: Add a new version sysctl to control child runs first
Date: Mon, 13 Sep 2021 10:13:54 +0200	[thread overview]
Message-ID: <YT8IQioxUARMus9w@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210912041222.59480-1-yang.yang29@zte.com.cn>

On Sun, Sep 12, 2021 at 04:12:23AM +0000, cgel.zte@gmail.com wrote:
> From: Yang Yang <yang.yang29@zte.com.cn>
> 
> The old version sysctl has some problems. First, it allows set value
> bigger than 1, which is unnecessary. Second, it didn't follow the
> rule of capabilities. Thirdly, it didn't use static key. This new
> version fixes all the problems.

Does any of that actually matter?

  reply	other threads:[~2021-09-13  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12  4:12 [PATCH] sched: Add a new version sysctl to control child runs first cgel.zte
2021-09-13  8:13 ` Peter Zijlstra [this message]
2021-09-13 11:37   ` CGEL
2021-09-13 13:42     ` Peter Zijlstra
2021-09-14  4:05       ` CGEL
     [not found]       ` <20210914040524.GA141438@cgel.zte@gmail.com>
2021-10-07  3:26         ` CGEL

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=YT8IQioxUARMus9w@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=cgel.zte@gmail.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=joshdon@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.hailong6@zte.com.cn \
    --cc=mcgrof@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=pjt@google.com \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=yang.yang29@zte.com.cn \
    --cc=yzaikin@google.com \
    --cc=zealci@zte.com.cm \
    /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;
as well as URLs for NNTP newsgroup(s).