Multiprogramming - Revision history

M4gnum0n: R section

2015-02-11T13:24:47Z

R section

← Previous revision		Revision as of 13:24, 11 February 2015
Line 1:		Line 1:
	#Redirect [[Computer_multitasking#Multiprogramming]]		#Redirect [[Computer_multitasking#Multiprogramming]] {{R section}}

Jamesx12345: ←Redirected page to Computer multitasking#Multiprogramming

2013-03-08T16:33:56Z

←Redirected page to Computer multitasking#Multiprogramming

← Previous revision		Revision as of 16:33, 8 March 2013
Line 1:		Line 1:
			#Redirect [[Computer_multitasking#Multiprogramming]]
	{{Mergeto\|Computer multitasking\|date=February 2010}}
	{{Unreferenced\|date=December 2009}}
	Computer '''multiprogramming''' is the allocation of computing resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature). It is distinguishable from '''monoprogramming''' (or '''uniprogramming''') in which only a single program may be run at a time.

	In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense.

	Initially, multiprogramming was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction. Multiprogramming was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s. The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.

	== Multiprogramming vs multitasking ==

	Multiprogramming should be differentiated from multitasking. A program generally comprises numerous ''tasks'', or steps in the execution of the program. Tasks frequently end with a request for input or output. In multiprogramming, the operating system identifies opportunities to interrupt one program and transfer control to another ''between tasks'' (e.g., when it is waiting for input/output). When this may occur is dependent upon the design of the programs being handled; a program may run for many hours before there is a chance to interrupt. By contrast, in [[Computer multitasking\|multitasking]] this transfer of control is independent of the program design. Switches between programs usually occur rapidly to create the illusion that they are running concurrently.


	[[Category:Computer architecture]]

	[[es:Multiprogramación]]
	[[eu:Multiprogramazio]]
	[[ru:Мультипрограммирование]]

92.100.179.116: interwiki

2013-02-16T12:48:51Z

interwiki

← Previous revision		Revision as of 12:48, 16 February 2013
Line 16:		Line 16:
	[[es:Multiprogramación]]		[[es:Multiprogramación]]
	[[eu:Multiprogramazio]]		[[eu:Multiprogramazio]]
			[[ru:Мультипрограммирование]]

Gnathan87: monoprogramming/uniprogramming

2013-01-08T17:04:16Z

monoprogramming/uniprogramming

← Previous revision		Revision as of 17:04, 8 January 2013
Line 1:		Line 1:
	{{Mergeto\|Computer multitasking\|date=February 2010}}		{{Mergeto\|Computer multitasking\|date=February 2010}}
	{{Unreferenced\|date=December 2009}}		{{Unreferenced\|date=December 2009}}
	Computer '''multiprogramming''' is the allocation of computing resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).		Computer '''multiprogramming''' is the allocation of computing resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature). It is distinguishable from '''monoprogramming''' (or '''uniprogramming''') in which only a single program may be run at a time.

	In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense.		In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense.

Gnathan87: /* Multiprogramming vs multitasking */

2013-01-08T01:15:47Z

Multiprogramming vs multitasking

← Previous revision		Revision as of 01:15, 8 January 2013
Line 9:		Line 9:
	== Multiprogramming vs multitasking ==		== Multiprogramming vs multitasking ==

	Multiprogramming should be differentiated from ~~multi-tasking~~. A program generally comprises numerous ''tasks'', or steps in the execution of the program. Tasks frequently end with a request for input or output. In multiprogramming, the operating system identifies opportunities to interrupt one program and transfer control to another ''between tasks'' (e.g., when it is waiting for input/output). When this may occur is dependent upon the design of the programs being handled; a program may run for many hours before there is a chance to interrupt. By contrast, in [[Computer multitasking\|~~Multi-tasking~~]] this transfer of control is independent of the program design. Switches between programs usually occur rapidly to create the illusion that they are running concurrently.		Multiprogramming should be differentiated from multitasking. A program generally comprises numerous ''tasks'', or steps in the execution of the program. Tasks frequently end with a request for input or output. In multiprogramming, the operating system identifies opportunities to interrupt one program and transfer control to another ''between tasks'' (e.g., when it is waiting for input/output). When this may occur is dependent upon the design of the programs being handled; a program may run for many hours before there is a chance to interrupt. By contrast, in [[Computer multitasking\|multitasking]] this transfer of control is independent of the program design. Switches between programs usually occur rapidly to create the illusion that they are running concurrently.

Gnathan87: copyediting

2013-01-08T01:14:26Z

copyediting

← Previous revision		Revision as of 01:14, 8 January 2013
Line 1:		Line 1:
	{{Mergeto\|Computer multitasking\|date=February 2010}}		{{Mergeto\|Computer multitasking\|date=February 2010}}
	{{Unreferenced\|date=December 2009}}		{{Unreferenced\|date=December 2009}}
	Computer '''multiprogramming''' is the allocation of ~~a computer system and its~~ resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).		Computer '''multiprogramming''' is the allocation of computing resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).

	~~Initially~~, this ~~technology~~ was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction. Multiprogramming was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s. The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.		In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense.

			Initially, multiprogramming was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction. Multiprogramming was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s. The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.

	== Multiprogramming vs multitasking ==		== Multiprogramming vs multitasking ==

			Multiprogramming should be differentiated from multi-tasking. A program generally comprises numerous ''tasks'', or steps in the execution of the program. Tasks frequently end with a request for input or output. In multiprogramming, the operating system identifies opportunities to interrupt one program and transfer control to another ''between tasks'' (e.g., when it is waiting for input/output). When this may occur is dependent upon the design of the programs being handled; a program may run for many hours before there is a chance to interrupt. By contrast, in [[Computer multitasking\|Multi-tasking]] this transfer of control is independent of the program design. Switches between programs usually occur rapidly to create the illusion that they are running concurrently.
	Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.

	In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense. A program generally comprises numerous ''tasks'', a task being a relatively small group of processor instructions which together achieve a definable logical step in the completion of a job or the execution of a continuous-running application program. A task frequently ends with some request requiring the moving of data, a convenient opportunity to allow another program to have system resources, particularly [[CPU time]].

	In multiprogramming, concurrent running (sharing of the processor) is achieved when the operating system identifies opportunities to interrupt the handling of one program ''between tasks'' (e.g., when it is waiting for input/output) and to transfer process control to another program (application, job or user). To a great extent, the ability of a system to share its resources equitably—or according to certain priorities—is dependent upon the design of the programs being handled and how frequently they may be interrupted. [[Computer multitasking\|Multi-tasking]] eliminates that dependency and expands upon multiprogramming by enabling the operating system [[supervisory program\|supervisor]] to interrupt programs in the middle of tasks and to transfer processor control so rapidly that each program is now assured a portion of each processing second, making the interruptions imperceptible to most human-interactive applications.

	[[Category:Computer architecture]]		[[Category:Computer architecture]]

Gnathan87 at 00:53, 8 January 2013

2013-01-08T00:53:48Z

← Previous revision		Revision as of 00:53, 8 January 2013
Line 3:		Line 3:
	Computer '''multiprogramming''' is the allocation of a computer system and its resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).		Computer '''multiprogramming''' is the allocation of a computer system and its resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).

	Initially, this technology was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction. Multiprogramming was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s.		Initially, this technology was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction. Multiprogramming was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s. The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.

			== Multiprogramming vs multitasking ==
	The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.

	Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.		Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.

	In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense.		In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense. A program generally comprises numerous ''tasks'', a task being a relatively small group of processor instructions which together achieve a definable logical step in the completion of a job or the execution of a continuous-running application program. A task frequently ends with some request requiring the moving of data, a convenient opportunity to allow another program to have system resources, particularly [[CPU time]].

	A program generally comprises numerous ''tasks'', a task being a relatively small group of processor instructions which together achieve a definable logical step in the completion of a job or the execution of a continuous-running application program. A task frequently ends with some request requiring the moving of data, a convenient opportunity to allow another program to have system resources, particularly [[CPU time]].

	In multiprogramming, concurrent running (sharing of the processor) is achieved when the operating system identifies opportunities to interrupt the handling of one program ''between tasks'' (e.g., when it is waiting for input/output) and to transfer process control to another program (application, job or user). To a great extent, the ability of a system to share its resources equitably—or according to certain priorities—is dependent upon the design of the programs being handled and how frequently they may be interrupted.		In multiprogramming, concurrent running (sharing of the processor) is achieved when the operating system identifies opportunities to interrupt the handling of one program ''between tasks'' (e.g., when it is waiting for input/output) and to transfer process control to another program (application, job or user). To a great extent, the ability of a system to share its resources equitably—or according to certain priorities—is dependent upon the design of the programs being handled and how frequently they may be interrupted. [[Computer multitasking\|Multi-tasking]] eliminates that dependency and expands upon multiprogramming by enabling the operating system [[supervisory program\|supervisor]] to interrupt programs in the middle of tasks and to transfer processor control so rapidly that each program is now assured a portion of each processing second, making the interruptions imperceptible to most human-interactive applications.

	[[Computer multitasking\|Multi-tasking]] eliminates that dependency and expands upon multiprogramming by enabling the operating system [[supervisory program\|supervisor]] to interrupt programs in the middle of tasks and to transfer processor control so rapidly that each program is now assured a portion of each processing second, making the interruptions imperceptible to most human-interactive applications.

	[[Category:Computer architecture]]		[[Category:Computer architecture]]

Ericbrunstad at 14:26, 18 December 2012

2012-12-18T14:26:13Z

← Previous revision		Revision as of 14:26, 18 December 2012
Line 3:		Line 3:
	Computer '''multiprogramming''' is the allocation of a computer system and its resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).		Computer '''multiprogramming''' is the allocation of a computer system and its resources to more than one concurrent ''application'', ''job'' or ''user'' ("program" in this nomenclature).

	Initially, this technology was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s.		Initially, this technology was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction. Multiprogramming was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s.

	The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.		The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.

117.234.171.51 at 16:42, 13 December 2012

2012-12-13T16:42:38Z

← Previous revision		Revision as of 16:42, 13 December 2012
Line 5:		Line 5:
	Initially, this technology was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s.		Initially, this technology was sought in order to optimize use of a computer system, since time and processing resources were often wasted when a single job waited for human interaction was developed as a feature of operating systems in the late 1950s and came into common use in [[mainframe computing]] in the mid- to late 1960s. This followed the development of hardware systems that possessed the requisite circuit logic and instruction sets to facilitate the transfer of control between the operating system and one or more independent applications, users or [[job stream]]s.

	The use of multiprogramming was enhanced by the arrival of [[virtual memory]] and [[virtual machine]] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.		The use of multiprogramming was enhanced by the arrival of [virtual memory] and [virtual machine] technology, which enabled individual programs to make use of memory and operating system resources as if other concurrently running programs were, for all practical purposes, non-existent and invisible to them.

	Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.		Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.

ClueBot NG: Reverting possible vandalism by 14.98.214.187 to version by 125.22.43.24. False positive? Report it. Thanks, ClueBot NG. (1374060) (Bot)

2012-12-03T10:14:43Z

Reverting possible vandalism by 14.98.214.187 to version by 125.22.43.24. False positive? Report it. Thanks, ClueBot NG. (1374060) (Bot)

← Previous revision		Revision as of 10:14, 3 December 2012
Line 9:		Line 9:
	Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.		Multiprogramming should be differentiated from multi-tasking since ''not all'' multiprogramming entails—or has the capability for-- "true" multi-tasking. This is the case even though the use of multi-tasking generally implies the use of some multiprogramming methods.

	In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense. yo		In this context, the root word "program" does not necessarily refer to a compiled application, rather, any set of commands submitted for execution by a user or operator. Such "program" could include a script or [[job control\|job control stream]] and any included calls to [[macro-instructions]], [[system utility\|system utilities]] or [[application program]] modules. An entire, interactive, logged-in user session can be thought of as a "program" in this sense.

	A program generally comprises numerous ''tasks'', a task being a relatively small group of processor instructions which together achieve a definable logical step in the completion of a job or the execution of a continuous-running application program. A task frequently ends with some request requiring the moving of data, a convenient opportunity to allow another program to have system resources, particularly [[CPU time]].		A program generally comprises numerous ''tasks'', a task being a relatively small group of processor instructions which together achieve a definable logical step in the completion of a job or the execution of a continuous-running application program. A task frequently ends with some request requiring the moving of data, a convenient opportunity to allow another program to have system resources, particularly [[CPU time]].