NUCLEUS - Revision history

Tingo: add product number section, and link to products

2020-07-05T22:20:28Z

add product number section, and link to products

← Older revision		Revision as of 22:20, 5 July 2020
Line 36:		Line 36:
	* nkClose – Close a port, a message, or a send reference.		* nkClose – Close a port, a message, or a send reference.
	* nkVersion – Get version of different NUCLEUS parts (kernel, library..).		* nkVersion – Get version of different NUCLEUS parts (kernel, library..).

			== Product numbers ==
			* [[:Category:ND-250295\|ND-250295]]

	==References==		==References==
	<references/>		<references/>
	[[Category:Glossary]]		[[Category:Glossary]]

TArntsen: Use standard headers (== not =, and === not ==), and re-word headers

2016-05-26T06:37:06Z

Use standard headers (== not =, and === not ==), and re-word headers

← Older revision		Revision as of 06:37, 26 May 2016
Line 1:		Line 1:
	'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[Multi-Function bus\|MF-Bus]] memory (former [[MPM-5]]), or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>{{ND-doc\|820026.1\|preface}}</ref>.		'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[Multi-Function bus\|MF-Bus]] memory (former [[MPM-5]]), or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>{{ND-doc\|820026.1\|preface}}</ref>.

	=~~NUCLEUS purpose~~=		==Purpose==
	NUCLEUS is intended for communication between processes within one computer. Unlike [[XMSG]], it cannot be used between computers. "Computer" in this context means one or several main CPUs with access to the same physical memory and OCTOBUS.		NUCLEUS is intended for communication between processes within one computer. Unlike [[XMSG]], it cannot be used between computers. "Computer" in this context means one or several main CPUs with access to the same physical memory and OCTOBUS.

	=~~NUCLEUS components~~=		==Components==

	==Kernel==		===Kernel===
	NUCLEUS data structures / messages are passed through shared memory (MPM), and managed via OCTOBUS.		NUCLEUS data structures / messages are passed through shared memory (MPM), and managed via OCTOBUS.

	==Library==		===Library===
	Applications will interface to the NUCLEUS kernel through libraries. Applications are isolated from the physical implementation of NUCLEUS which differs between ND-500 and ND-5000.		Applications will interface to the NUCLEUS kernel through libraries. Applications are isolated from the physical implementation of NUCLEUS which differs between ND-500 and ND-5000.

	==Monitor==		===Monitor===
	The NUCLEUS monitor is a tool for inspection of parts of the NUCLEUS kernel, e.g. message queues.		The NUCLEUS monitor is a tool for inspection of parts of the NUCLEUS kernel, e.g. message queues.

	=~~NUCLEUS concepts~~=		==Concepts==
	Communication between processes is based on ports and messages. Ports and messages have descriptions in physical memory (the NUCLEUS kernel). A port is a defined communication port between processes, and it can be given a name. A message is constructed as a buffer for data, and a header. The header may contain e.g. a description of the data, and it can also link to other messages.		Communication between processes is based on ports and messages. Ports and messages have descriptions in physical memory (the NUCLEUS kernel). A port is a defined communication port between processes, and it can be given a name. A message is constructed as a buffer for data, and a header. The header may contain e.g. a description of the data, and it can also link to other messages.

	An application can create a message, and then link it to a port. The port could be owned by another process. Messages are queued in the sequence they arrive.		An application can create a message, and then link it to a port. The port could be owned by another process. Messages are queued in the sequence they arrive.

	=Difference between ND-500 and ND-5000=		==Difference between ND-500 and ND-5000==
	Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging do not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>{{ND-doc\|820026.1\|NUCLEUS Overview}}</ref>.		Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging do not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>{{ND-doc\|820026.1\|NUCLEUS Overview}}</ref>.

	=~~NUCLEUS~~ functions=		==Library functions==
	* nkCrePort – Create a new port. The creating process becomes port owner.		* nkCrePort – Create a new port. The creating process becomes port owner.
	* nkCreName – Assign a name to a port, so that other processes can refer to it.		* nkCreName – Assign a name to a port, so that other processes can refer to it.
Line 37:		Line 37:
	* nkVersion – Get version of different NUCLEUS parts (kernel, library..).		* nkVersion – Get version of different NUCLEUS parts (kernel, library..).

	=References=		==References==
	<references/>		<references/>
	[[Category:Glossary]]		[[Category:Glossary]]

Tingo: added Glossary category

2014-07-23T21:41:50Z

added Glossary category

← Older revision		Revision as of 21:41, 23 July 2014
Line 39:		Line 39:
	=References=		=References=
	<references/>		<references/>
			[[Category:Glossary]]

TArntsen: Fix: does -> do

2012-08-18T19:51:27Z

Fix: does -> do

← Older revision		Revision as of 19:51, 18 August 2012
Line 21:		Line 21:

	=Difference between ND-500 and ND-5000=		=Difference between ND-500 and ND-5000=
	Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging ~~does~~ not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>{{ND-doc\|820026.1\|NUCLEUS Overview}}</ref>.		Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging do not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>{{ND-doc\|820026.1\|NUCLEUS Overview}}</ref>.

	=NUCLEUS functions=		=NUCLEUS functions=

TArntsen: Fixed typo: MPF->MPM. Also slightly rewritten because MF-Bus is actually the newer term for MPM-5 according to [1]

2009-09-20T15:04:59Z

Fixed typo: MPF->MPM. Also slightly rewritten because MF-Bus is actually the newer term for MPM-5 according to [1]

← Older revision		Revision as of 15:04, 20 September 2009
Line 1:		Line 1:
	'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[~~MPF~~-~~5]] aka~~ MF-Bus memory, or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>{{ND-doc\|820026.1\|preface}}</ref>.		'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[Multi-Function bus\|MF-Bus]] memory (former [[MPM-5]]), or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>{{ND-doc\|820026.1\|preface}}</ref>.

	=NUCLEUS purpose=		=NUCLEUS purpose=

Mike: Changing references to ND-doc

2009-09-20T09:15:40Z

Changing references to ND-doc

← Older revision		Revision as of 09:15, 20 September 2009
Line 1:		Line 1:
	'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[MPF-5]] aka MF-Bus memory, or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>~~DOMINO and NUCLEUS Software Guide~~ ND-820026.1, preface</ref>.		'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[MPF-5]] aka MF-Bus memory, or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>{{ND-doc\|820026.1\|preface}}</ref>.

	=NUCLEUS purpose=		=NUCLEUS purpose=
Line 21:		Line 21:

	=Difference between ND-500 and ND-5000=		=Difference between ND-500 and ND-5000=
	Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging does not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>~~DOMINO and NUCLEUS Software Guide~~ ND-820026.1, NUCLEUS Overview</ref>.		Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging does not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>{{ND-doc\|820026.1\|NUCLEUS Overview}}</ref>.

	=NUCLEUS functions=		=NUCLEUS functions=

Mike: Fixed some formatting and linking

2009-09-20T06:33:16Z

Fixed some formatting and linking

← Older revision		Revision as of 06:33, 20 September 2009
Line 1:		Line 1:
	NUCLEUS is a library for fast message passing on ND-500-II or ND-5000 computers. It can be used for message passing both in the ND-100 and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and MPF-5 aka MF-Bus memory, or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>DOMINO and NUCLEUS Software Guide ND-820026.1, preface</ref>.		'''NUCLEUS''' is a library for fast message passing on [[ND-500-II]] or [[ND-5000]] computers. It can be used for message passing both in the [[ND-100]] and in the ND-500/5000, but is not available on pure ND-100 computers: NUCLEUS requires either an ND-5000 with [[OCTOBUS]] and a [[DOMINO]] controller and [[MPF-5]] aka MF-Bus memory, or an ND-500-II with OCTOBUS alone (DOMINO is not available for ND-500)<ref>DOMINO and NUCLEUS Software Guide ND-820026.1, preface</ref>.

	=NUCLEUS purpose=		=NUCLEUS purpose=

TArntsen: Changed function list to use bullets, removed

2009-09-17T15:52:41Z

Changed function list to use bullets, removed <br>

TArntsen: More accurate about 500/5000 NUCLEUS differences

2009-09-16T15:13:58Z

More accurate about 500/5000 NUCLEUS differences

← Older revision		Revision as of 15:13, 16 September 2009
Line 21:		Line 21:

	=Difference between ND-500 and ND-5000=		=Difference between ND-500 and ND-5000=
	Due to the DOMINO I/O controllers used in ND-5000, NUCLEUS messaging does not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs ~~also has~~ NUCLEUS support in the microcode<ref>DOMINO and NUCLEUS Software Guide ND-820026.1, NUCLEUS Overview</ref>.		Due to the DOMINO I/O controllers used in ND-5000, time-critical parts of NUCLEUS messaging does not have to go through the ND-100 (via a monitor call), so NUCLEUS communication between ND-5000 processes is faster and has less overhead than communication between ND-500 processes. ND-5000 CPUs have NUCLEUS support in the microcode for the time-critical functions<ref>DOMINO and NUCLEUS Software Guide ND-820026.1, NUCLEUS Overview</ref>.

	=NUCLEUS functions=		=NUCLEUS functions=

TArntsen: Typo: the->they

2009-09-16T14:37:18Z

Typo: the->they

← Older revision		Revision as of 14:37, 16 September 2009
Line 18:		Line 18:
	Communication between processes is based on ports and messages. Ports and messages have descriptions in physical memory (the NUCLEUS kernel). A port is a defined communication port between processes, and it can be given a name. A message is constructed as a buffer for data, and a header. The header may contain e.g. a description of the data, and it can also link to other messages.		Communication between processes is based on ports and messages. Ports and messages have descriptions in physical memory (the NUCLEUS kernel). A port is a defined communication port between processes, and it can be given a name. A message is constructed as a buffer for data, and a header. The header may contain e.g. a description of the data, and it can also link to other messages.

	An application can create a message, and then link it to a port. The port could be owned by another process. Messages are queued in the sequence ~~the~~ arrive.		An application can create a message, and then link it to a port. The port could be owned by another process. Messages are queued in the sequence they arrive.

	=Difference between ND-500 and ND-5000=		=Difference between ND-500 and ND-5000=

← Older revision		Revision as of 15:52, 17 September 2009
Line 24:		Line 24:

	=NUCLEUS functions=		=NUCLEUS functions=
	nkCrePort – Create a new port. The creating process becomes port owner.~~<br>~~		* nkCrePort – Create a new port. The creating process becomes port owner.
	nkCreName – Assign a name to a port, so that other processes can refer to it.~~<br>~~		* nkCreName – Assign a name to a port, so that other processes can refer to it.
	nkOpenPort – Get a send reference to a named port.~~<br>~~		* nkOpenPort – Get a send reference to a named port.
	nkOpenReturnPort – Get a send reference to the home port or last sender of a message.~~<br>~~		* nkOpenReturnPort – Get a send reference to the home port or last sender of a message.
	nkDelName – Delete the symbolic name of a port. The port itself is not removed.~~<br>~~		* nkDelName – Delete the symbolic name of a port. The port itself is not removed.
	nkCreMessage – Allocate a message buffer in a contiguous area of physical memory.~~<br>~~		* nkCreMessage – Allocate a message buffer in a contiguous area of physical memory.
	nkMove – Write, read, or insert data into or from a message buffer.~~<br>~~		* nkMove – Write, read, or insert data into or from a message buffer.
	nkSend – Send a message to a port.~~<br>~~		* nkSend – Send a message to a port.
	nkReceive – The first message in the queue to a port is received.~~<br>~~		* nkReceive – The first message in the queue to a port is received.
	nkGetInfo – Get information about the specified message or port.~~<br>~~		* nkGetInfo – Get information about the specified message or port.
	nkClose – Close a port, a message, or a send reference.~~<br>~~		* nkClose – Close a port, a message, or a send reference.
	nkVersion – Get version of different NUCLEUS parts (kernel, library..).~~<br>~~		* nkVersion – Get version of different NUCLEUS parts (kernel, library..).

	=References=		=References=
	<references/>		<references/>