From: Tony Lindgren <tony@atomide.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: 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>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
Thomas Renninger <trenn@suse.de>
Subject: Re: Dynamic tick for 2.6.14 - what's the plan?
Date: Wed, 31 Aug 2005 10:44:19 +0300 [thread overview]
Message-ID: <20050831074419.GA1029@atomide.com> (raw)
In-Reply-To: <200508301701.49228.s0348365@sms.ed.ac.uk>
* Alistair John Strachan <s0348365@sms.ed.ac.uk> [050830 18:57]:
> On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
> [snip]
> > >
> > > Same issue, it's waiting on dynticks before being reworked.
> >
> > Also one more minor issue; Dyntick can cause slow boots with dyntick
> > enabled from boot because the there's not much in the timer queue
> > until init.
> >
> > This probably does not show up much on x86 though because of the
> > short hardware timers.
>
> You could disable it until jiffies >= 0; this covers the boot criteria and
> still allows for moderate savings post boot (though maybe on embedded systems
> the delay is too long?).
Yeah, that's true. Or just enable it from an init script via sysfs.
Tony
next prev parent reply other threads:[~2005-08-31 7:45 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 [this message]
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
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=20050831074419.GA1029@atomide.com \
--to=tony@atomide.com \
--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=trenn@suse.de \
--cc=tytso@mit.edu \
--cc=vatsa@in.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox