linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Balbir Singh <bsingharora@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] proc/schedstat: Expose /proc/<pid>/schedstat if delay accounting is enabled
Date: Thu, 25 Jun 2015 11:40:46 -0700	[thread overview]
Message-ID: <CAM_iQpXd6_1Ry1WxfMUbjnwhm=7teM8NHsgutw_qHvgjwU78TA@mail.gmail.com> (raw)
In-Reply-To: <20150625182707.GA15883@naverao1-tp.in.ibm.com>

On Thu, Jun 25, 2015 at 11:27 AM, Naveen N. Rao
<naveen.n.rao@linux.vnet.ibm.com> wrote:
>
> The primary issue with CONFIG_SCHEDSTATS is the (slight) additional
> overhead it introduces, per Kconfig. Due to this, it is not enabled by
> default by some of the distro kernels.
>

The overhead is same for CONFIG_TASK_DELAY_ACCT since the
core sched info code is protected by CONFIG_TASK_DELAY_ACCT
or CONFIG_TASK_DELAY_ACCT?

  reply	other threads:[~2015-06-25 18:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25  7:12 [PATCH] proc/schedstat: Expose /proc/<pid>/schedstat if delay accounting is enabled Naveen N. Rao
2015-05-28  5:11 ` Naveen N. Rao
2015-05-28  9:11 ` Balbir Singh
2015-05-29  6:16   ` Naveen N. Rao
2015-05-29  8:04     ` Ingo Molnar
2015-05-29  8:55       ` Naveen N. Rao
2015-05-29  9:18         ` Ingo Molnar
2015-05-29  9:45           ` Naveen N. Rao
2015-05-29  9:54             ` Ingo Molnar
2015-05-29 17:06               ` Naveen N. Rao
2015-06-02  7:58                 ` Ingo Molnar
2015-06-25  8:39                   ` Naveen N. Rao
2015-06-25 12:12                     ` Ingo Molnar
2015-06-25 18:00   ` Cong Wang
2015-06-25 18:27     ` Naveen N. Rao
2015-06-25 18:40       ` Cong Wang [this message]
2015-06-26  8:39         ` Naveen N. Rao

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='CAM_iQpXd6_1Ry1WxfMUbjnwhm=7teM8NHsgutw_qHvgjwU78TA@mail.gmail.com' \
    --to=xiyou.wangcong@gmail.com \
    --cc=bsingharora@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@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 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).