mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Ignacio Vazquez-Abrams <ignacio@openservices.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: adding accuracy to random timers on PPC - new config option or  runtime overhead?
Date: Wed, 22 Aug 2001 13:51:03 -0400	[thread overview]
Message-ID: <3B83F107.61FD47A0@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108221335000.12521-100000@terbidium.openservices.net>

Ignacio Vazquez-Abrams wrote:
> 
> On Wed, 22 Aug 2001, Chris Friesen wrote:
> > I'm looking at putting in PPC-specific code in add_timer_randomness() that would
> > be similar to the x86-specific stuff.
> >
> > The problem is that the PPC601 uses real time clock registers while the other
> > PPC chips use a timebase register, so two different versions will be required.
> > Should I try and identify at runtime which it is (which would be extra
> > overhead), or should I add another config option to the kernel?

> How about determining which one to use at boot time? That way there's no
> overhead, and there's no need to have yet another config option which probably
> doesn't need to be there.

As far as I can see there will still be some extra overhead.  We'd need an extra
conditional that wouldn't be there with the config option.  Granted, one
conditional shouldn't be too expensive, especially since we'll always be picking
the same branch.

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

  reply	other threads:[~2001-08-22 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 17:31 Chris Friesen
2001-08-22 17:36 ` Ignacio Vazquez-Abrams
2001-08-22 17:51   ` Chris Friesen [this message]
2001-08-22 17:57     ` Ignacio Vazquez-Abrams
2001-08-23  8:15 ` Gabriel Paubert

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=3B83F107.61FD47A0@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=ignacio@openservices.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®