Gerrit Huizenga wrote: > +As with any other resource under the CKRM framework, numtasks also assigns > +all the resources to the detault class(/rcfs/taskclass). Since , the number > +of tasks in a system is not limited, this resource controller provides a > +way to set the total number of tasks available in the system through the > config > +file. By default this value is 128k(131072). In other words, if not changed, > +the total number of tasks allowed in a system is 131072. > + > +The config variable that affect this is sys_total_tasks.
Because there are people who do not want to use the numtask controller, no limit is a preferable default value for sys_total_tasks. > +Usage > +----- > + > +For brevity, unless otherwise specified all the following commands are > +executed in the default class (/rcfs/taskclass). > + > +As explained above the config file shows sys_total_tasks and forkrate > +info. > + > + # cd /rcfs/taskclass > + # cat config > + > res=numtasks,sys_total_tasks=131072,forkrate=1000000,forkrate_interval=3600 > + > +By default, the sys_total_tasks is set to 131072(128k), and forkrate is set > +to 1 million and forkrate_interval is set to 3600 seconds. Which means the > +total number of tasks in a system is limited to 131072 and the forks are > +limited to 1 million per hour. >From the same point of view, the default value of forkrate should be no limit. (In addition, 1 million tasks per hour is not an abnormally high rate.) Thanks, MAEDA Naoaki ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
