From: npunmia@hss.hns.com
To: linux-kernel@vger.kernel.org
Subject: 1.6666.... ms interrupts needed!!
Date: Mon, 9 Apr 2001 17:15:53 +0530 [thread overview]
Message-ID: <65256A29.003F97A4.00@sandesh.hss.hns.com> (raw)
Hi.
We are simulating air interface of GPRS on LAN. A TDMA(time division multiple
access) frame duration is 40ms. Each TDMA frame consists of 24 timeslots. Each
timeslot is of 40/24 ms (i.e 1.66666.......ms) . To know what current
timeslot it is, we need a timer interrupt after every 1.6666... ms . Since we
are implementing this on LAN, minor jitters once in a while can be tolerated
(say 0.2 ms more or less once a while would be OK).
As of now, we are modifying the HZ value in param.h to 600. This gives us
a CPU tick of 1.6666.... ms. (i.e 1/600sec). I want to know if it would affect
the perfomance of the CPU.
Is there a better way to achieve the granularity of 1.666...ms . Would the
UTIME patch be a better way from performance or any other point of view than
this method?
With Regards,
Niraj Punmia
reply other threads:[~2001-04-09 11:49 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=65256A29.003F97A4.00@sandesh.hss.hns.com \
--to=npunmia@hss.hns.com \
--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®