update dynalloc.shtml

doc/html/dynalloc.shtml

@@ -60,7 +60,7 @@ the response message could be like: "avail_nodes=4 avail_slots=16"</p>
 app (application) part. 
 For example:<br>
 "allocate jobid=100 return=all timeout=10:app=0 np=5 N=2 node_list=vm[2-3]
-flag=mandatory:app=1 N=2"</p>
+flag=mandatory cpu_bind=cores mem_per_cpu=100:app=1 N=2"</p>
 
 <p>In the job part of the above message, <b>jobid</b> is optional and will 
 be sent back to client for identifying the allocation results; the <b>return</b>
@@ -87,14 +87,20 @@ from <b>node_list</b>; else if "flag=optional", try best to allocate node
 from <b>node_list</b>, and the allocation should include all nodes in the 
 given list that are currently available, if that is not enough to meet the 
 requested node number <b>N</b>, then take any other nodes that are available
-to fill out the requested number.
+to fill out the requested number. <b>cpu_bind</b> is to bind tasks to CPUs, 
+which is used only when the task/affinity or task/cgroup plugin is enabled 
+(please refer to 'man salloc'). <b>mem_per_cpu</b> is mimimum memory required
+per allocated CPU in MegaBytes, which is used when the task/cgroup plugin is 
+enabled.
 </p>
 
-<p>Note that in the response message, e.g., "jobid=100:app=0 slurm_jobid=679 
-allocated_node_list=vm2,vm3 tasks_per_node=3,2:app=1 slurm_jobid=680 
-allocated_node_list=vm4,vm5 tasks_per_node=4(x2)", each allocation result 
-for an app will also include a <b>slurm_jobid</b> which will be used for 
-later resource deallocation.</p>
+<p>A response message might be like "jobid=100:app=0 slurm_jobid=679 
+allocated_node_list=vm2,vm3 tasks_per_node=3,2:app=1 allocate_failure". 
+In this example, 'app=0' gets a successful allocation while the allocation 
+for 'app=1' fails. <b>Note that</b> in the response message with successful
+allocation for an app, a <b>slurm_jobid</b> is returned for later operation, 
+e.g., process launch, resource deallocation, etc.
+</p>
 
 <p class="footer"><a href="#top">top</a>