All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Question about /proc/uptime
Date: Fri, 27 Dec 2013 15:45:04 +0100	[thread overview]
Message-ID: <20131227144504.GA17192@redhat.com> (raw)
In-Reply-To: <1388025009.1176.17@driftwood>

Add Frederic, I am not sure I understand this correctly.

On 12/25, Rob Landley wrote:
>
> There are two values here, the first is seconds since boot time (which
> is just elapsed time; at one point it was ajusted for suspend and that
> was revered as confusing).

Hmm, uptime_proc_show() still uses get_monotonic_boottime(), this should
include suspend time?

> The second value isn't documented but looking at fs/proc/uptime.c I
> think it's idle time?

And this cpustat[CPUTIME_IDLE] doesn't match get_idle_time(), I guess
it only counts ticks.

> Except, if yo uadd up the idle time from all
> processors wouldn't you get 4x the uptime on a 4-way SMP system that's
> been idle since boot?

Yes, looks strange.

> Also, is this actual "cpu was on but not doing anything" time, so
> doesn't count suspend as idle?

I think suspend is not counted as idle.

> Confused,

I guess the 2nd value is historical, probably you should use /proc/stat.

Oleg.


  reply	other threads:[~2013-12-27 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  2:30 Question about /proc/uptime Rob Landley
2013-12-27 14:45 ` Oleg Nesterov [this message]
2013-12-30  8:56   ` Martin Schwidefsky
2013-12-30 15:11     ` Oleg Nesterov
2013-12-30 15:26       ` Martin Schwidefsky
2014-01-01  4:17         ` Rob Landley
2014-01-01 12:41           ` Martin Schwidefsky
2014-01-01 21:21             ` Rob Landley
2014-01-02  8:28               ` Martin Schwidefsky

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=20131227144504.GA17192@redhat.com \
    --to=oleg@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=schwidefsky@de.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.