From: Ingo Oeser <ioe-lkml@rameria.de>
To: john stultz <johnstul@us.ibm.com>, Tomas Janousek <tjanouse@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, tsmetana@redhat.com,
riel@redhat.com
Subject: Re: [PATCH] Introduce boot based time
Date: Fri, 11 May 2007 00:22:54 +0200 [thread overview]
Message-ID: <200705110022.55862.ioe-lkml@rameria.de> (raw)
In-Reply-To: <1178827376.6011.11.camel@localhost.localdomain>
Hi John and Tomas,
On Thursday 10 May 2007, john stultz wrote:
> I'm not sure I follow this.
>
> total_sleep_time stores seconds. So on 32bit systems that's 130some
> years, so it shouldn't be an issue.
>
> Is the reason you want it to be a ktime is because you want a way to
> keep sub-second sleep granularity?
No, I'm just overworked and getting sloppy :-/
Sorry for the noise...
Best regards
Ingo Oeser
next prev parent reply other threads:[~2007-05-10 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 15:03 Broken process startup times after suspend (regression) Tomas Janousek
2007-05-03 19:59 ` john stultz
2007-05-04 16:13 ` Tomas Janousek
2007-05-04 18:18 ` john stultz
2007-05-04 19:09 ` Tomas Janousek
2007-05-10 17:10 ` [PATCH] Introduce boot based time Tomas Janousek
2007-05-10 17:10 ` [PATCH] Use boot based time for process start time and boot time in /proc Tomas Janousek
2007-05-10 18:44 ` john stultz
2007-05-10 23:40 ` Andrew Morton
2007-05-11 8:45 ` Tomas Janousek
2007-05-11 19:51 ` Andrew Morton
2007-05-11 23:37 ` Tomas Janousek
2007-05-11 8:46 ` Tomas Janousek
2007-05-10 17:10 ` [PATCH] Use boot based time for uptime " Tomas Janousek
2007-05-10 18:47 ` john stultz
2007-05-10 18:42 ` [PATCH] Introduce boot based time john stultz
2007-05-10 19:48 ` Ingo Oeser
2007-05-10 20:00 ` Tomas Janousek
2007-05-10 20:02 ` john stultz
2007-05-10 22:22 ` Ingo Oeser [this message]
2007-05-10 23:40 ` Andrew Morton
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=200705110022.55862.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tjanouse@redhat.com \
--cc=tsmetana@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 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®