OS Overhead

[Job Cacka]

I think there is a Linux distribution called Real Time Linux that would suit
an application that was time sensitive like this. A Real Time OS is your
best bet with this type of application.

Job Cacka

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com]On Behalf Of Burke, Thomas G.
Sent: Monday, January 30, 2006 12:37 PM
To: General Red Hat Linux discussion list
Subject: OS Overhead


All,

	This is a somewhat convoluted question, but here goes...

	We are creating a system that has a "timeline" (e.g. tasks must
be completed in a given amount of time)

	OK, so we have a processor (we'll stay generic at this point)
that will be running a linux based kernel, and we want to figure out how
much processor availability we have (e.g. clock tics in a given time).

	We know that the kernel functions (including resource
allocation, interrupt hadling, and so on) take up some omount of CPU
horsepower (albeit small)

	What is a good general rule of thumb for a barebones linux
system?  I know this is gross estimation, but does the kernel use up 20%
of my CPU resources?  10%?  Any ideas?

	Thanks
		Tom
--
redhat-list mailing list
unsubscribe
mailto:redhat-list-request at redhat.com?subjecthttps://www.redhat.com/mailman/
listinfo/redhat-list