From 4b44aa0fb8d668517d361bfe04fb482f4ad0d20a Mon Sep 17 00:00:00 2001
From: patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>
Date: Thu, 5 Nov 2009 23:14:34 +0000
Subject: [PATCH] Document workqueue configuration

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2231 42af7a65-404d-4744-a932-0658087f49c3
---
 Documentation/NuttxPortingGuide.html | 32 ++++++++++++++++++++++++++--
 1 file changed, 30 insertions(+), 2 deletions(-)

diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html
index dec31beea36..c3093d8b783 100644
--- a/Documentation/NuttxPortingGuide.html
+++ b/Documentation/NuttxPortingGuide.html
@@ -12,7 +12,7 @@
       <h1><big><font color="#3c34ec">
         <i>NuttX RTOS Porting Guide</i>
       </font></big></h1>
-      <p>Last Updated: September 15, 2009</p>
+      <p>Last Updated: November 5, 2009</p>
     </td>
   </tr>
 </table>
@@ -2124,12 +2124,40 @@ extern void up_ledoff(int led);
     <code>CONFIG_SDCLONE_DISABLE</code>: Disable cloning of all socket
     desciptors by task_create() when a new task is started.
     If set, all sockets will appear to be closed in the new task.
-  </li>: 
+  </li>
   <li>
     <code>CONFIG_NXFLAT</code>: Enable support for the NXFLAT binary format.
     This format will support execution of NuttX binaries located
     in a ROMFS filesystem (see <code>examples/nxflat</code>).
   </li>
+  <li>
+    <code>CONFIG_SCHED_WORKQUEUE</code>: Create a dedicated "worker" thread to
+    handle delayed processing from interrupt handlers.  This feature
+    is required for some drivers but, if there are not complaints,
+    can be safely disabled.  The worker thread also performs
+    garbage collection -- completing any delayed memory deallocations
+    from interrupt handlers.  If the worker thread is disabled,
+    then that clean will be performed by the IDLE thread instead
+    (which runs at the lowest of priority and may not be appropriate
+    if memory reclamation is of high priority).  If CONFIG_SCHED_WORKQUEUE
+    is enabled, then the following options can also be used:
+  </li>
+  <li>
+    <code>CONFIG_SCHED_WORKPRIORITY</code>: The execution priority of the worker
+    thread.  Default: 50
+  </li>
+  <li>
+    <code>CONFIG_SCHED_WORKPERIOD</code>: How often the worker thread checks for
+    work.  Default: 50 MS.
+  </li>
+  <li>
+    <code>CONFIG_SCHED_WORKSTACKSIZE</code>: The stack size allocated for the worker
+    thread.  Default: CONFIG_IDLETHREAD_STACKSIZE.
+  </li>
+  <li>
+    <code>CONFIG_SIG_SIGWORK</code>: The signal number that will be used to wake-up
+    the worker thread.  Default: 4
+  </li>
 </ul>
 
 <p>