22:
95:
of threads to perform this work. Either the work units themselves or the threads that perform the work can be referred to as "tasks", and these can be referred to respectively as requests/responses/threads, incoming tasks/completed tasks/threads (as illustrated), or requests/responses/tasks.
217:
A unit of computation. In a parallel job, two or more concurrent tasks work together through message passing and shared memory. Although it is common to allocate one task per physical or logical processor, the terms "task" and "processor" are not
261:(at least since v2.6.13, up to and including v4.8) to refer to a unit of execution, which may share various system resources with other tasks on the system. Depending on the level of sharing, the task may be regarded as a conventional
184:
serves as both a unit of work and the mechanism for executing it. In the executor framework, the unit of work and the execution mechanism are separate. The key abstraction is the unit of work, which is called a
143:
individual tasks can correspond to a single step of processing a single item in a batch, or to a single step of processing all items in the batch. In online systems, tasks most commonly correspond to a single
233:"In a multiprogramming or multiprocessing environment, one or more sequences of instructions treated by a control program as an element of work to be accomplished by a computer."
313:(MVT). In this case tasks were identified with light-weight processes, a job consisted of a number of tasks, and, later, tasks could have sub-tasks (in modern terminology,
139:
In the sense of "unit of work", in a job (meaning "one-off piece of work") a task can correspond to a single step (the step itself, not the execution thereof), while in
172:
programming language, these two concepts (unit of work and unit of execution) are conflated when working directly with threads, but clearly distinguished in the
201:
use of the term has been influential, though underlining the ambiguity of the term, in IBM terminology, "task" has dozens of specific meanings, including:
440:
237:
The term task in OS/360 through z/OS is roughly equivalent to light-weight process; the tasks in a job step share an address space. However, in
469:
465:
214:
A set of actions designed to achieve a particular result. A task is performed on a set of targets on a specific schedule.
293:
The serial model has the ability to process tasks of one job in an independent manner similar to the functioning of the
407:
576:
173:
556:
169:
481:
503:
454:
310:
306:
329:
302:
242:
157:
125:
54:
321:
149:
79:
64:
221:
An activity that has business value, is initiated by a user, and is performed by software.
8:
266:
109:
59:
262:
113:
69:
525:
357:
286:
140:
117:
105:
121:
382:
570:
337:
314:
273:
system call, where a user can specify the desired level of resource sharing.
132:
at the same time – but has nuances of the work sense of multiple tasks being
57:
or a unit of work. The term is ambiguous; precise alternative terms include
432:
258:
160:), either a single stage of handling, or the whole system-wide handling.
92:
26:
362:
345:
88:
30:
46:
245:(SRB) may have access to other address spaces via its access list.
320:
Today the term "task" is used very ambiguously. For example, the
294:
238:
21:
128:" primarily refers to the processing sense – multiple tasks
226:
205:
A unit of work representing one of the steps in a process.
91:
of incoming work to do and outgoing completed work, and a
208:
A unit of work to be accomplished by a device or process.
198:
550:
336:
to execute in future, what is traditionally known as a
124:, with the task itself typically a process. The term "
553:
Simultaneous multiprogramming of electronic computers
348:" is commonly used in the sense of "units of work".
301:The term was popularized with the introduction of
289:in the early 1960s, as in this example from 1961:
211:A process and the procedures that run the process.
41:(yellow), in the sense of task as "unit of work".
568:
311:Multiprogramming with a Variable number of Tasks
87:(for work). In the adjacent diagram, there are
307:Multiprogramming with a Fixed number of Tasks
269:. Tasks are brought into existence using the
104:In the sense of "unit of execution", in some
383:"What is task? - Definition from WhatIs.com"
526:"clone, __clone2 - create a child process"
229:specifically, it is defined precisely as:
120:), a task is a unit of execution within a
466:Glossary of z/OS terms and abbreviations
20:
180:When you work directly with threads, a
569:
16:Unit of execution or work in software
13:
514:. Linus Torvalds. October 3, 2016.
492:. Linus Torvalds. August 29, 2005.
344:extension. By contrast, the term "
193:
14:
588:
551:James Larrimore McKenney (1961).
431:
305:(announced 1964), which featured
116:. In non-interactive execution (
248:
544:
518:
496:
474:
459:
447:
425:
408:"What are computer processes?"
400:
375:
108:, a task is synonymous with a
99:
1:
368:
285:for a part of a job dates to
7:
351:
163:
10:
593:
439:(Third ed.). p.
276:
530:Linux Programmer's Manual
241:through z/OS, a task or
112:, and in others with a
330:Windows Task Scheduler
299:
191:
42:
577:Computing terminology
506:include/linux/sched.h
484:include/linux/sched.h
291:
243:Service Request Block
178:
158:information retrieval
37:(blue) and completed
24:
322:Windows Task Manager
152:architectures) or a
65:light-weight process
29:(green boxes) with
324:manages (running)
136:at the same time.
43:
453:IBM Terminology:
106:operating systems
73:(for execution),
584:
561:
560:
548:
542:
541:
539:
537:
522:
516:
515:
507:
500:
494:
493:
485:
478:
472:
463:
457:
451:
445:
444:
429:
423:
422:
420:
418:
404:
398:
397:
395:
393:
379:
358:Task parallelism
343:
287:multiprogramming
272:
218:interchangeable.
183:
150:request–response
141:batch processing
118:batch processing
592:
591:
587:
586:
585:
583:
582:
581:
567:
566:
565:
564:
549:
545:
535:
533:
532:. July 17, 2016
524:
523:
519:
505:
502:
501:
497:
483:
480:
479:
475:
464:
460:
452:
448:
430:
426:
416:
414:
412:liutilities.com
406:
405:
401:
391:
389:
381:
380:
376:
371:
354:
341:
340:, and uses the
315:child processes
279:
270:
257:is used in the
251:
196:
194:IBM terminology
181:
166:
102:
17:
12:
11:
5:
590:
580:
579:
563:
562:
543:
517:
495:
473:
458:
446:
437:Effective Java
424:
399:
373:
372:
370:
367:
366:
365:
360:
353:
350:
278:
275:
250:
247:
235:
234:
223:
222:
219:
215:
212:
209:
206:
195:
192:
165:
162:
101:
98:
15:
9:
6:
4:
3:
2:
589:
578:
575:
574:
572:
558:
554:
547:
531:
527:
521:
513:
509:
499:
491:
487:
477:
471:
467:
462:
456:
450:
442:
438:
434:
433:Bloch, Joshua
428:
413:
409:
403:
388:
384:
378:
374:
364:
361:
359:
356:
355:
349:
347:
339:
338:job scheduler
335:
331:
327:
323:
318:
316:
312:
308:
304:
298:
296:
290:
288:
284:
274:
268:
264:
260:
256:
246:
244:
240:
232:
231:
230:
228:
220:
216:
213:
210:
207:
204:
203:
202:
200:
190:
188:
177:
175:
171:
161:
159:
155:
151:
147:
142:
137:
135:
131:
127:
123:
119:
115:
111:
107:
97:
94:
90:
86:
82:
81:
76:
72:
71:
66:
62:
61:
56:
53:is a unit of
52:
48:
40:
36:
32:
28:
23:
19:
552:
546:
534:. Retrieved
529:
520:
511:
498:
489:
476:
461:
449:
436:
427:
415:. Retrieved
411:
402:
390:. Retrieved
386:
377:
333:
325:
319:
300:
292:
282:
280:
259:Linux kernel
254:
252:
249:Linux kernel
236:
224:
197:
186:
179:
167:
153:
145:
138:
133:
129:
126:multitasking
103:
84:
78:
74:
68:
58:
50:
44:
38:
34:
18:
536:November 6,
176:framework:
100:Terminology
93:thread pool
33:of waiting
31:task queues
27:thread pool
555:. p.
512:GitHub.com
490:GitHub.com
443:, Item 68.
387:WhatIs.com
369:References
363:Task queue
346:task queue
332:schedules
309:(MFT) and
326:processes
281:The term
253:The term
174:Executors
134:performed
130:executing
55:execution
47:computing
25:A sample
571:Category
417:June 11,
392:June 11,
352:See also
334:programs
328:, while
164:Examples
295:IBM 709
277:History
271:clone()
267:process
239:MVS/ESA
168:In the
146:request
110:process
80:request
60:process
441:p. 272
303:OS/360
263:thread
182:Thread
114:thread
89:queues
70:thread
199:IBM's
154:query
85:query
83:, or
39:tasks
35:tasks
538:2016
419:2015
394:2015
342:.job
283:task
255:task
227:z/OS
187:task
170:Java
156:(in
148:(in
75:step
51:task
49:, a
557:154
317:).
265:or
225:In
122:job
45:In
573::
528:.
510:.
488:.
468::
435:.
410:.
385:.
77:,
67:,
63:,
559:.
540:.
508:"
504:"
486:"
482:"
470:T
455:T
421:.
396:.
297:.
189:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
