All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [sched next] overflowed cpu time for kernel threads in /proc/PID/stat
Date: Tue, 3 Sep 2013 20:32:29 +0200	[thread overview]
Message-ID: <20130903183229.GB30757@gmail.com> (raw)
In-Reply-To: <20130903180912.GA2340@swordfish>


* Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:

> On (09/03/13 10:43), Stanislaw Gruszka wrote:
> > Ok, I see now, utime is 0 . This seems to be problem with dynamic ticks
> > as you told that your application is kernel compilation, so we utilize
> > lot of cpu time in user-space.
> > 
> > Anyway we should handle utime == 0 situation on scaling code. We work
> > well when rtime & stime are not big (variables and results fit in
> > 32 bit), otherwise we have that stime bigger than rtime problem. Let's
> > try to handle the problem by below patch. Sergey, does it work for you ?
> 
> checked on -current and -next -- works fine, good job.
> 
> here are my:
> Reported-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Tested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>

Cool and thanks for the patient reporting and testing!

Stanislaw, mind sending a changelogged, signed off patch with Sergey's 
tags included? It also warrants a -stable backport tag I think.

Thanks,

	Ingo

  reply	other threads:[~2013-09-03 18:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 11:14 [sched next] overflowed cpu time for kernel threads in /proc/PID/stat Sergey Senozhatsky
2013-08-20 15:15 ` Frederic Weisbecker
2013-08-20 15:35   ` Sergey Senozhatsky
2013-08-20 15:42     ` Frederic Weisbecker
2013-08-20 15:53       ` Sergey Senozhatsky
2013-08-20 18:48       ` Sergey Senozhatsky
2013-08-21 15:39       ` Sergey Senozhatsky
2013-08-30 23:04         ` Frederic Weisbecker
2013-08-31 19:01           ` Sergey Senozhatsky
2013-09-08 10:56             ` Frederic Weisbecker
2013-09-08 10:59             ` Frederic Weisbecker
2013-09-02 12:28           ` Sergey Senozhatsky
2013-09-02 13:07             ` Frederic Weisbecker
2013-09-02 13:39               ` Sergey Senozhatsky
2013-09-02 13:50               ` Stanislaw Gruszka
2013-09-02 14:00                 ` Sergey Senozhatsky
2013-09-03  8:43                   ` Stanislaw Gruszka
2013-09-03  9:33                     ` Sergey Senozhatsky
2013-09-03 13:15                     ` Sergey Senozhatsky
2013-09-03 18:09                     ` Sergey Senozhatsky
2013-09-03 18:32                       ` Ingo Molnar [this message]
2013-09-04 12:08                         ` [PATCH -tip] sched/cputime: do not scale when utime == 0 Stanislaw Gruszka
2013-09-04 12:33                           ` Ingo Molnar
2013-09-04 13:16                             ` [PATCH -tip v2] " Stanislaw Gruszka
2013-09-04 14:31                               ` Ingo Molnar
2013-09-04 14:37                               ` [tip:timers/urgent] sched/cputime: Do " tip-bot for Stanislaw Gruszka
2013-09-04 15:35                                 ` Frederic Weisbecker
2013-09-02 14:13                 ` [sched next] overflowed cpu time for kernel threads in /proc/PID/stat Frederic Weisbecker
2013-09-02 14:24                   ` Sergey Senozhatsky

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=20130903183229.GB30757@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sgruszka@redhat.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.