change log for rtems (2011-05-18)

[rtems-vc at rtems.org]

 *joel*:
2011-05-18	Joel Sherrill <joel.sherrill at oarcorp.com>

	* user/conf.t: Add SMP Configuration parameters.

M  1.309  doc/ChangeLog
M   1.70  doc/user/conf.t

diff -u rtems/doc/ChangeLog:1.308 rtems/doc/ChangeLog:1.309
--- rtems/doc/ChangeLog:1.308	Wed May 18 18:00:49 2011
+++ rtems/doc/ChangeLog	Wed May 18 18:29:12 2011
@@ -1,5 +1,9 @@
 2011-05-18	Joel Sherrill <joel.sherrill at oarcorp.com>
 
+	* user/conf.t: Add SMP Configuration parameters.
+
+2011-05-18	Joel Sherrill <joel.sherrill at oarcorp.com>
+
 	* user/conf.t: Slight rework to deemphasize not using confdefs.h
 
 2011-05-12	Joel Sherrill <joel.sherrilL at OARcorp.com>

diff -u rtems/doc/user/conf.t:1.69 rtems/doc/user/conf.t:1.70
--- rtems/doc/user/conf.t:1.69	Wed May 18 18:00:50 2011
+++ rtems/doc/user/conf.t	Wed May 18 18:29:12 2011
@@ -402,11 +402,12 @@
 
 @findex CONFIGURE_SCHEDULER_PRIORITY
 @item Deterministic Priority Scheduler - This is the default scheduler
-in RTEMS and is designed for predictable performance under the highest
-loads.  It can block or unblock a thread in a constant amount of time.
-This scheduler requires a variable amount of memory based upon the number
-of priorities configured in the system.  This scheduler may be explicitly
-selected by defining @code{CONFIGURE_SCHEDULER_PRIORITY}.
+in RTEMS for single core applications and is designed for predictable
+performance under the highest loads.  It can block or unblock a thread
+in a constant amount of time.  This scheduler requires a variable
+amount of memory based upon the number of priorities configured in
+the system.  This scheduler may be explicitly selected by defining
+ at code{CONFIGURE_SCHEDULER_PRIORITY}.
 
 @findex CONFIGURE_SCHEDULER_SIMPLE
 @item Simple Priority Scheduler - This is an alternative scheduler
@@ -418,6 +419,23 @@
 for use in small systems where RAM is limited.  This scheduler may be explicitly
 selected by defining @code{CONFIGURE_SCHEDULER_SIMPLE}.
 
+ at findex CONFIGURE_SCHEDULER_SIMPLE_SMP
+ at item Simple SMP Priority Scheduler - This scheduler is derived from the
+Simple Priority Scheduler but is capable of scheduling threads across
+multiple cores.  It is designed to provide the same task scheduling
+behaviour as the Deterministic Priority Scheduler while distributing
+threads across multiple cores.  Being based upon the Simple Priority
+Scheduler, it is also maintains a single sorted list of all ready threads.
+Thus blocking or unblocking a thread is not a constant time operation
+with this scheduler.  In addition, when allocating threads to cores,
+the algorithm is not constant time.  This algorithm was not designed
+with efficiency as a primary design goal.  Its primary design goal was to
+provide an SMP-aware scheduling algorithm that is simple to understand.
+This scheduler is currently the default in SMP configurations and is
+only selected when @code{CONFIGURE_SMP_APPLICATION} is defined.  In a
+configuration with SMP enabled at configure time, it may be explicitly
+selected by defining @code{CONFIGURE_SCHEDULER_SIMPLE_SMP}.
+
 @end itemize
 
 The pluggable scheduler interface was added after the 4.10 release series
@@ -453,6 +471,26 @@
 @c
 @c
 @c
+ at subsection SMP Specific Configuration Parameters
+
+When RTEMS is configured to support SMP target systems, there are other
+configuration parameters which apply.
+
+ at itemize @bullet
+
+ at findex CONFIGURE_SMP_APPLICATION
+ at item @code{CONFIGURE_SMP_APPLICATION} must be defined if the application
+is to make use of multiple CPU cores in an SMP target system.
+
+ at item @code{CONFIGURE_SMP_MAXIMUM_PROCESSORS} must be set to the number
+of CPU cores in the SMP configuration.  If there are more cores available
+than configured, the rest will be ignored.
+
+ at end itemize
+
+ at c
+ at c
+ at c
 @subsection Device Driver Table
 
 This section defines the configuration parameters related



--

Generated by Deluxe Loginfo [http://www.codewiz.org/projects/index.html#loginfo] 2.122 by Bernardo Innocenti <bernie at develer.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/vc/attachments/20110518/208e7a8a/attachment-0001.html>