CPU load
Date: Thu, 9 Jun 2005 16:01:04 +0200
Hi
we are going to develop a linux based system. It will be the first one
within our company. At the moment, we are defining the HW/SW modules and
related tasks to design in. I'm trying to find out the overall CPU load we
will have in the system to be able to decide on an appropriate CPU(s) to
use.
Does anybody out there has any (coarse) benchmarks for the necessary
minimum CPU load we have to preserve if implementing
USB2.0 stack
IEEE1394 stack
TCP/IP stack
Thanks in advance
Joe
Relevant Pages
- Re: Need some help understanding array definitions
... Data structures defined with VARIABLE, CREATE, VALUE, CONSTANT, and related words are, indeed, all global. ... Unlike some languages, Forth doesn't discourage defining global data structures, but it's important to understand their proper use. ... They provide for "persistent" data, as well as space for strings and arrays. ... Strings and arrays should be in defined data structures and referenced by address and length or address on the stack. ... (comp.lang.forth) - Pratap PattnaiK - IBM Fellow
... Dr. Pratap Pattnaik has been appointed an IBM Fellow for his technical ... leadership in defining and optimizing the stack for IBM's enterprise server ... He has been the chief architect and scientist for defining, ... Pattnaik's contributions span across the enterprise stack of systems, ... (bit.listserv.ibm-main) - Re: 200x wish list
... define a stack effect for it. ... things on the control-flow stack. ... VARIABLE DEFINING? ... error to compile anything without a definition started to compile it ... (comp.lang.forth) - Re: CPU load
... > we are going to develop a linux based system. ... I'm trying to find out the overall CPU load we ... > IEEE1394 stack ... If more than one item has a time-critical component then you ... (comp.os.linux.embedded) - Re: CREATE
... desired behaviors, defining and instance. ... This works particularly well with optimizing compilers. ... Here the first line gives the defining behavior, and the second defines the instance behavior. ... We don't conventionally show this in the stack comment, because the purpose of the stack comment is to tell the user *what happens*, not how it works internally. ... (comp.lang.forth) |
|