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