All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Mike Galbraith <mgalbraith@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] sched: Make schedstats a runtime tunable that is disabled by default v3
Date: Wed, 3 Feb 2016 09:15:26 +0000	[thread overview]
Message-ID: <20160203091526.GO8337@techsingularity.net> (raw)
In-Reply-To: <20160202144514.GA28611@linux.vnet.ibm.com>

On Tue, Feb 02, 2016 at 08:15:14PM +0530, Srikar Dronamraju wrote:
> > Yes. This on top? It's not completely bullet proof as a user could both
> > force schedstat disabled and enable sleep profiling but it's a waste of
> > memory to guard against it
> > 
> > diff --git a/include/linux/sched.h b/include/linux/sched.h
> > index a10494a94cc3..5c2cd37c42e9 100644
> > --- a/include/linux/sched.h
> > +++ b/include/linux/sched.h
> > @@ -920,6 +920,14 @@ static inline int sched_info_on(void)
> >  #endif
> >  }
> > 
> > +#ifdef CONFIG_SCHEDSTATS
> > +void force_schedstat_enabled(void);
> > +#else
> > +static inline void force_schedstat_enabled(void)
> > +{
> > +}
> > +#endif
> 
> One nit:
> Since force_schedstat_enabled is called under CONFIG_SCHEDSTATS
> we may not want the static define.
> 

I'm not sure I get this either :(. It is a static inline that does
nothing under !CONFIG_SCHEDSTAT because tehre is nothing to do.
Otherwise it needs to be available for profiling and I just spotted it's
needed by latencytop too.

-- 
Mel Gorman
SUSE Labs

      reply	other threads:[~2016-02-03  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01  9:37 [PATCH 1/1] sched: Make schedstats a runtime tunable that is disabled by default v3 Mel Gorman
2016-02-01 14:17 ` Matt Fleming
2016-02-02  9:32 ` Srikar Dronamraju
2016-02-02 11:58   ` Mel Gorman
2016-02-02 14:45     ` Srikar Dronamraju
2016-02-03  9:15       ` Mel Gorman [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=20160203091526.GO8337@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mgalbraith@suse.de \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.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.