From: Marcus Sundberg <marcus@ingate.com>
To: lartc@vger.kernel.org
Subject: [LARTC] PSCHED_CLOCK_SOURCE
Date: Tue, 06 Aug 2002 13:29:51 +0000 [thread overview]
Message-ID: <marc-lartc-102864064528397@msgid-missing> (raw)
Hi,
just wondering whether my assumption that, assuming an IA32 machine
with working TSC, using PSCHED_CLOCK_SOURCE = PSCHED_CPU will give
significantly better accuracy and at least as good performance as
using PSCHED_CLOCK_SOURCE = PSCHED_JIFFIES?
//Marcus
--
---------------------------------------+--------------------------
Marcus Sundberg <marcus@ingate.com> | Firewalls with SIP & NAT
Firewall Developer, Ingate Systems AB | http://www.ingate.com/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-08-06 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102864064528397@msgid-missing \
--to=marcus@ingate.com \
--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.