RE: OS Overhead

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@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx]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@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/
listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Relevant Pages

  • Re: Embedded Linux Vs. Real time Linux
    ... Because we do have some hard real time demands (caused by our hardware ... I don't see any reason why this code need to run outside the Linux ... kernel enviroment. ...
    (comp.os.linux.embedded)
  • Re: All RTOS (linux Based ) Other than RT-Linux
    ... systemswhich should have total linux compatible other than RT- ... If that is what you mean, all linuxes are real time. ... IMO these requirements cannot be satisfied with the public Linux code, and also cannot be introduced by simple patches to the kernel etc. sources. ... IMO it then is inevitable to split RT applications into an RT process, running under control of the RT kernel, and an non-RT process, running under control of the Linux kernel. ...
    (comp.os.linux.setup)
  • NYC LOCAL: Wednesday 21 April 2004 NYLUG Meeting: Mark Slater on Linux in Real Time
    ... Mark Slater on Linux in Real Time ... 590 Madison Avenue at 57th Street ... hyperthreading control and CPU shielding. ...
    (comp.os.linux.misc)
  • NYC LOCAL: Wednesday 21 April 2004 NYLUG Meeting: Mark Slater on Linux in Real Time
    ... Mark Slater on Linux in Real Time ... 590 Madison Avenue at 57th Street ... hyperthreading control and CPU shielding. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Linux Vs vxWorks
    ... Linux is now more or less equal to vxWorks ... Till the time you talk about soft real time it is very subjected to ... Linux is soft real time and vxWorks ...
    (comp.os.vxworks)