kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: is the tickless kernel now the "standard"?
Date: Sun, 15 May 2011 11:01:12 -0700	[thread overview]
Message-ID: <20110515180112.GA21222@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105151344490.26511@localhost6.localdomain6>

On Sun, May 15, 2011 at 01:48:43PM -0400, Robert P. J. Day wrote:
> On Sun, 15 May 2011, Greg KH wrote:
> 
> > On Sun, May 15, 2011 at 12:41:30PM -0400, Robert P. J. Day wrote:
> > >
> > >   given that ubuntu ships with the kernel configured for tickless
> > > behaviour, and that RHEL6 also ships tickless, is it safe to say that
> > > tickless is now the standard configuration?  is there a compelling
> > > reason to *not* run tickless with the latest 2.6 kernels?
> >
> > Yes it is the "standard" and no, there is not any reason to not enable
> > it.  Unless you like burning extra power for no reason.
> 
>   ok, good to know.  i assume, then, that it's fairly pointless to use
> the value of "jiffies" for anything that requires even moderate
> accuracy.  i was poking around the timer code, and i can see this in
> kernel/time/timekeeping.c:

No, never access jiffies directly, use the correct delay and timer
functions instead, they will handle things properly.  And that's the way
to get correct accuracy if you need it.

thanks,

greg k-h

  reply	other threads:[~2011-05-15 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 16:41 is the tickless kernel now the "standard"? Robert P. J. Day
2011-05-15 16:56 ` Greg KH
2011-05-15 17:48   ` Robert P. J. Day
2011-05-15 18:01     ` Greg KH [this message]
2011-05-16  4:42       ` Michael Blizek
2011-05-16  4:46         ` Michael Blizek

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=20110515180112.GA21222@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).