public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Tony Lindgren <tony@atomide.com>,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	Con Kolivas <kernel@kolivas.org>, "Theodore Ts'o" <tytso@mit.edu>,
	Christopher Friesen <cfriesen@nortel.com>,
	Lee Revell <rlrevell@joe-job.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Renninger <trenn@suse.de>
Subject: Re: Dynamic tick for 2.6.14 - what's the plan?
Date: Wed, 31 Aug 2005 16:47:05 +0530	[thread overview]
Message-ID: <20050831111705.GC10307@in.ibm.com> (raw)
In-Reply-To: <1125486186.3213.8.camel@laptopd505.fenrus.org>

On Wed, Aug 31, 2005 at 01:03:05PM +0200, Arjan van de Ven wrote:
> that sounds like a fundamental issue that really needs to be fixed
> first!

It should be fixed by the patch here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=111556608901657&w=2

Tony,
	I don't see any slow bootups on x86 because of dyn-tick.
If you still see them in your env, can you test with the patch above?

Recovering time after sleep is the single biggest problem that I seem
to have, even while using ACPI PM timer (forget TSC). Time can
drift by couple of seconds after few hours. I have made
some changes to the lost tick calculation in timer_pm.c after which
it seems to be stable on some machines, but I cant repeat that
on other (maybe newer) machines. Will post out all the changes I have
pretty soon.

-- 


Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017

  reply	other threads:[~2005-08-31 11:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29 22:26 Dynamic tick for 2.6.14 - what's the plan? Lee Revell
2005-08-29 22:42 ` Christopher Friesen
2005-08-30  0:05   ` Con Kolivas
2005-08-30  2:54     ` Theodore Ts'o
2005-08-30  3:48       ` Con Kolivas
2005-08-30 12:31         ` Tony Lindgren
2005-08-30 16:01           ` Alistair John Strachan
2005-08-31  7:44             ` Tony Lindgren
2005-08-31  8:39               ` Arjan van de Ven
2005-08-31 10:34                 ` Tony Lindgren
2005-08-31 10:50                   ` Srivatsa Vaddagiri
2005-08-31 11:03                   ` Arjan van de Ven
2005-08-31 11:17                     ` Srivatsa Vaddagiri [this message]
2005-08-31 11:20                       ` Srivatsa Vaddagiri
2005-08-31 13:21                         ` Tony Lindgren
2005-09-01  6:36                           ` Tony Lindgren
2005-08-31 17:39   ` Srivatsa Vaddagiri
2005-08-31 17:42     ` Christopher Friesen

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=20050831111705.GC10307@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=arjan@infradead.org \
    --cc=cfriesen@nortel.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=tony@atomide.com \
    --cc=trenn@suse.de \
    --cc=tytso@mit.edu \
    /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