All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Larroy <piotr@omega.resa.es>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Can Athlon Thunderbird 1.4GHZ use PSCHED_CPU?
Date: Wed, 13 Nov 2002 01:54:55 +0000	[thread overview]
Message-ID: <marc-lartc-103715260302734@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103686345710584@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

On Sat, Nov 09, 2002 at 09:36:43AM -0800, gypsy wrote:
> The docs in linux/include/net/sched/pkt_sched.h and in tc/README.last 
> only speak about Intel CPUs.  Can I use PSCHED_CPU with my Athlon 
> Thunderbird 1.4GHZ CPU?

Yes.


> 
> A better question is: What Bad Thing Happens when
> #define PSCHED_CLOCK_SOURCE PSCHED_CPU 
> but there is no timestamp counter (TSC) or the TSC is broken?
> 
> How would I know?

try or read proccessor specs

> 
> TIA,
> gypsy
> --
> A: Because it reverses the logical flow of conversation.
> Q: Why is top posting frowned upon?
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

-- 
O   _____________________________________________________________   O
|  /-| Pedro Larroy Tovar. PiotR | http://omega.resa.es/piotr  |-\  |
| /--|            No MS-Office attachments please.             |--\ |
o-|--|              e-mail: piotr@omega.resa.es                |--|-o 
   \-|   finger piotr@omega.resa.es for public key and info    |-/  
    -------------------------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-11-13  1:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09 17:36 [LARTC] Can Athlon Thunderbird 1.4GHZ use PSCHED_CPU? gypsy
2002-11-13  1:54 ` Pedro Larroy [this message]

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=marc-lartc-103715260302734@msgid-missing \
    --to=piotr@omega.resa.es \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.