All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: rjw@rjwysocki.net, mingo@redhat.com, bp@suse.de, x86@kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, peterz@infradead.org,
	jolsa@redhat.com,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH v6 5/9] x86/sysctl: Add sysctl for ITMT scheduling feature
Date: Wed, 26 Oct 2016 10:59:33 -0700	[thread overview]
Message-ID: <1477504773.2680.22.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1610261231250.4983@nanos>

On Wed, 2016-10-26 at 12:49 +0200, Thomas Gleixner wrote:
> On Thu, 20 Oct 2016, Tim Chen wrote:
> > 
> > +static int sched_itmt_update_handler(struct ctl_table *table, int write,
> > +			      void __user *buffer, size_t *lenp, loff_t *ppos)
> Please align the arguments proper
> 
> static int
> sched_itmt_update_handler(struct ctl_table *table, int write,
> 			  void __user *buffer, size_t *lenp, loff_t *ppos)
> 

Okay.

> > 
> > +{
> > +	int ret;
> > +	unsigned int old_sysctl;
> 	unsigned int old_sysctl;
> 	int ret;
> 
> Please. It's way simpler to read.

Sure.

> 
> > 
> > -void sched_set_itmt_support(void)
> > +int sched_set_itmt_support(void)
> >  {
> >  	mutex_lock(&itmt_update_mutex);
> >  
> > +	if (sched_itmt_capable) {
> > +		mutex_unlock(&itmt_update_mutex);
> > +		return 0;
> > +	}
> > +
> > +	itmt_sysctl_header = register_sysctl_table(itmt_root_table);
> > +	if (!itmt_sysctl_header) {
> > +		mutex_unlock(&itmt_update_mutex);
> > +		return -ENOMEM;
> > +	}
> > +
> >  	sched_itmt_capable = true;
> >  
> > +	/*
> > +	 * ITMT capability automatically enables ITMT
> > +	 * scheduling for small systems (single node).
> > +	 */
> > +	if (topology_num_packages() == 1)
> > +		sysctl_sched_itmt_enabled = 1;
> I really hate this. This is policy and the kernel should not impose
> policy. Why would I like to have this enforced on my single socket XEON
> server?
> 
> > 
> > +	if (sysctl_sched_itmt_enabled) {
> Why would sysctl_sched_itmt_enabled be true at this point, aside of the
> above policy imposement?

That's true, it will only be enabled for the above case.  I can merge
it into the if check above.


Tim

  parent reply	other threads:[~2016-10-26 17:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 21:59 [PATCH v6 0/9] Support Intel® Turbo Boost Max Technology 3.0 Tim Chen
2016-10-20 21:59 ` [PATCH v6 1/9] sched: Extend scheduler's asym packing Tim Chen
2016-10-26 10:27   ` Thomas Gleixner
2016-10-26 18:10     ` Tim Chen
2016-10-26 18:23       ` Thomas Gleixner
2016-10-20 21:59 ` [PATCH v6 2/9] x86/topology: Provide topology_num_packages() Tim Chen
2016-10-20 21:59 ` [PATCH v6 3/9] x86/topology: Define x86's arch_update_cpu_topology Tim Chen
2016-10-20 21:59 ` [PATCH v6 4/9] x86: Enable Intel Turbo Boost Max Technology 3.0 Tim Chen
2016-10-20 21:59 ` [PATCH v6 5/9] x86/sysctl: Add sysctl for ITMT scheduling feature Tim Chen
2016-10-26 10:49   ` Thomas Gleixner
2016-10-26 11:25     ` Peter Zijlstra
2016-10-26 11:24       ` Thomas Gleixner
2016-10-26 17:23         ` Tim Chen
2016-10-26 18:09           ` Thomas Gleixner
2016-10-27 19:32             ` Tim Chen
2016-10-26 17:59     ` Tim Chen [this message]
2016-10-26 10:52   ` Thomas Gleixner
2016-10-26 18:03     ` Tim Chen
2016-10-26 18:11       ` Thomas Gleixner
2016-10-26 19:38         ` Tim Chen
2016-10-20 22:00 ` [PATCH v6 6/9] x86/sched: Add SD_ASYM_PACKING flags to x86 ITMT CPU Tim Chen
2016-10-20 22:00 ` [PATCH v6 7/9] acpi: bus: Enable HWP CPPC objects Tim Chen
2016-10-20 22:00 ` [PATCH v6 8/9] acpi: bus: Set _OSC for diverse core support Tim Chen
2016-10-20 22:00 ` [PATCH v6 9/9] cpufreq: intel_pstate: Use CPPC to get max performance Tim Chen

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=1477504773.2680.22.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=bp@suse.de \
    --cc=jolsa@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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.