From: Robert Hancock <hancockrwd@gmail.com>
To: Junhee Lee <junhee@netsys.kaist.ac.kr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: microsecond event scheduling in an application
Date: Sun, 20 Sep 2009 12:26:09 -0600 [thread overview]
Message-ID: <4AB673C1.7020909@gmail.com> (raw)
In-Reply-To: <015f01ca3090$85e8a280$91b9e780$@kaist.ac.kr>
On 09/08/2009 08:27 AM, Junhee Lee wrote:
> I am working on event scheduler which handles events in microsecond level.
> Actual this program is a network emulator using simulation codes.
> I'd like to expect that network emulator is working as simulation behaviors.
> Thus high resolution timer interrupt is required.
> But high resolution timer interrupt derived by high tick frequency (jiffies
> clock) must effect the system performance.
> Are there any comments or ways to support microsecond event scheduling
> without performance degradation?
Just increasing HZ will degrade performance, yes, but we have hrtimers
now which should be able to use granularities smaller than one jiffy, so
it shouldn't be needed..
next prev parent reply other threads:[~2009-09-20 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 14:27 microsecond event scheduling in an application Junhee Lee
2009-09-20 18:26 ` Robert Hancock [this message]
2009-09-20 18:30 ` Arjan van de Ven
2009-09-22 6:35 ` Junhee Lee
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=4AB673C1.7020909@gmail.com \
--to=hancockrwd@gmail.com \
--cc=junhee@netsys.kaist.ac.kr \
--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