Changeset 90378e4 in rtems


Ignore:
Timestamp:
Nov 16, 1999, 4:23:26 PM (20 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, master
Children:
1dbf307
Parents:
4b960e5
Message:

Added BSP_MAXIMUM_OPERATION_COUNT and BSP_ITERATION_COUNT
which allow the BSP to override the default number of objects
that will be created in the timing tests. This is useful for
reducing memory consumption on small targets. The BSP_ITERATION_COUNT
can be used to reduce the number of repititions in some of the
tests. This is useful for extremely slow targets (we haven't seen
any slow enough to justify modifying this one yet though. :)

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • c/src/tests/tmtests/include/timesys.h

    r4b960e5 r90378e4  
    1818
    1919/*
    20  *   How many times a particular operation is performed while timed.
     20 *  This constant determines the maximum number of a resource
     21 *  that will be created.  For example, some test create multiple
     22 *  blocking tasks to determine the execution time of blocking
     23 *  services.  By default, the blocking time of 100 tasks will
     24 *  be measured.  Small targets often do not have enough memory
     25 *  to create 100 tasks.  By setting the BSP_MAXIMUM_OPERATION_COUNT
     26 *  to a lower number (typically 10), all of the time tests can be
     27 *  run.
    2128 */
    22  
     29
     30#ifndef BSP_MAXIMUM_OPERATION_COUNT
    2331#define OPERATION_COUNT 100
     32#else
     33#define OPERATION_COUNT 100 BSP_MAXIMUM_OPERATION_COUNT
     34#endif
     35
     36/*
     37 *  Some tests are repeated (iterated) multiple times over
     38 *  "operation count" operations.  For example, a semaphore
     39 *  test may acquire and release the semaphore "operation count"
     40 *  times per loop and the body of the loop is repeated "iteration
     41 *  count" times.  This value is a repitition factor which does
     42 *  not increase memory usage -- only execution time.
     43 */
     44
     45#ifndef BSP_ITERATION_COUNT
    2446#define IT_COUNT        100
     47#else
     48#define IT_COUNT BSP_ITERATION_COUNT
     49#endif
    2550
    2651/* functions */
  • testsuites/tmtests/include/timesys.h

    r4b960e5 r90378e4  
    1818
    1919/*
    20  *   How many times a particular operation is performed while timed.
     20 *  This constant determines the maximum number of a resource
     21 *  that will be created.  For example, some test create multiple
     22 *  blocking tasks to determine the execution time of blocking
     23 *  services.  By default, the blocking time of 100 tasks will
     24 *  be measured.  Small targets often do not have enough memory
     25 *  to create 100 tasks.  By setting the BSP_MAXIMUM_OPERATION_COUNT
     26 *  to a lower number (typically 10), all of the time tests can be
     27 *  run.
    2128 */
    22  
     29
     30#ifndef BSP_MAXIMUM_OPERATION_COUNT
    2331#define OPERATION_COUNT 100
     32#else
     33#define OPERATION_COUNT 100 BSP_MAXIMUM_OPERATION_COUNT
     34#endif
     35
     36/*
     37 *  Some tests are repeated (iterated) multiple times over
     38 *  "operation count" operations.  For example, a semaphore
     39 *  test may acquire and release the semaphore "operation count"
     40 *  times per loop and the body of the loop is repeated "iteration
     41 *  count" times.  This value is a repitition factor which does
     42 *  not increase memory usage -- only execution time.
     43 */
     44
     45#ifndef BSP_ITERATION_COUNT
    2446#define IT_COUNT        100
     47#else
     48#define IT_COUNT BSP_ITERATION_COUNT
     49#endif
    2550
    2651/* functions */
Note: See TracChangeset for help on using the changeset viewer.