mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Ken Chen <kenchen@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched: schedstat needs a diet
Date: Wed, 17 Oct 2007 09:23:24 +0200	[thread overview]
Message-ID: <20071017072323.GB18044@elte.hu> (raw)
In-Reply-To: <b040c32a0710161337l24d61d45h61be0ded72b54a9f@mail.gmail.com>


* Ken Chen <kenchen@google.com> wrote:

> schedstat is useful in investigating CPU scheduler behavior.  Ideally, 
> I think it is beneficial to have it on all the time.  However, the 
> cost of turning it on in production system is quite high, largely due 
> to number of events it collects and also due to its large memory 
> footprint.
> 
> Most of the fields probably don't need to be full 64-bit on 64-bit 
> arch.  Rolling over 4 billion events will most like take a long time 
> and user space tool can be made to accommodate that.  I'm proposing 
> kernel to cut back most of variable width on 64-bit system.  (note, 
> the following patch doesn't affect 32-bit system).

thanks, applied.

note that current -git has a whole bunch of new schedstats fields in 
/proc/<PID>/sched which can be used to track the exact balancing 
behavior of tasks. It can be cleared via echoing 0 to the file - so 
overflow is not an issue. Most of those new fields should probably be 
unsigned int too. (they are u64 right now.)

	Ingo

  reply	other threads:[~2007-10-17  7:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 20:37 Ken Chen
2007-10-17  7:23 ` Ingo Molnar [this message]
2007-10-17  9:29   ` Peter Zijlstra
2007-10-18 22:19     ` Mathieu Desnoyers
2007-10-18 22:57       ` Ken Chen
2007-10-18 23:13         ` Mathieu Desnoyers
2007-10-31  9:06         ` Rick Lindsley

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=20071017072323.GB18044@elte.hu \
    --to=mingo@elte.hu \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®