Lines Matching +full:system +full:- +full:control
1 .\" Copyright (c) 1996-1999 Whistle Communications, Inc.
19 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
47 system provides a uniform and modular system for the implementation
63 .Bl -bullet -compact
69 A common framework for kernel entities to inter-communicate.
71 A reasonably fast, kernel-based implementation.
90 In object-oriented language, types are classes, and nodes are instances
114 which is expressed as a 32-bit hexadecimal value.
128 .Bl -bullet
151 by the input queueing system, rather than being delivered directly.
157 in preference to the general node-wide methods.
167 control messages.
179 Along with data, nodes can also receive control messages.
180 There are generic and type-specific control messages.
181 Control messages have a common
182 header format, followed by type-specific data, and are binary structures
185 type-specific data between binary and
192 generic control messages below).
195 There are three ways to address a control message.
210 (or equivalent ID-based name) is used as the destination address
219 addressing modes are available to control programs outside the kernel;
225 control message is supplied with a
229 Each control message contains a 32-bit value, called a
241 This allows a message to be re-routed or passed on, should
245 messages for flow control and link management purposes are
246 defined by the base system that are usually
248 Flow control message would usually travel
254 That is, data and control messages are delivered by making function
289 By default, all control message packets are considered to be writers
299 .Bl -bullet
301 Whenever a node delivers a data or control message, the node
315 and some other part of the system.
335 device or system entity, or the thread is unable to acquire a lock on
382 .Bl -tag -width 2n
404 Tear-down is automatic.
447 .Bl -tag -width 2n
497 .Bf -symbolic
500 specific meta-data format is obsoleted now.
505 NETISR system (see below).
523 .It Receive control message
524 This method is called when a control message is addressed to the node.
527 is received, with a pointer to the control message.
549 All control messages and replies are
564 also be made known, which allows the use of such things as flow-control
616 .Bd -literal -offset indent
628 .Bd -literal
630 [ "Frame1" ](uplink)<-->(data)[<un-named>](dlci16)<-->(mux)[<un-named> ]
631 [ A ] [ B ](dlci20)<---+ [ C ]
634 +>(mux)[<un-named>]
638 One could always send a control message to node C from anywhere
658 .Em control messages .
663 This allows the option of hop-by-hop distribution of messages and
675 In a similar way, flow control messages may be routed in the reverse
705 .Bl -tag -width 2n
716 .Bl -tag -width 2n
738 .Bd -literal -offset indent
780 .Bl -tag -width 2n
823 Typically a node's private info contains a back-pointer to the node or hook
840 Control messages have the following structure:
841 .Bd -literal
865 Control messages have the fixed header shown above, followed by a
869 .Bl -tag -width indent
880 Indicates whether this is a command or a response control message.
887 The corresponding node type's unique 32-bit value.
900 The de-facto method for generating unique type cookies is to take the
924 .Ss Control Message ASCII Form
925 Control messages are in binary format for efficiency.
928 it, control messages may be converted to and from an equivalent
934 .Bl -enum
951 In general, the arguments field of a control message can be any
955 some pre-defined datatypes in
958 .Bl -bullet
994 .Ss Generic Control Messages
1000 .Bl -tag -width indent
1065 This message converts a binary control message to its
1068 The entire control message to be converted is contained within the
1072 If successful, the reply will contain the same control
1083 The entire control message to be converted, in
1097 contains the binary version of the control message.
1099 .Ss Flow Control Messages
1100 In addition to the control messages that affect nodes with respect to the
1102 .Em flow control
1106 handled automatically by the system, so
1108 flow control, and will be in the likely path of these messages.
1169 .Bl -tag -width indent
1185 socket is used for sending and receiving control messages.
1186 Data and control messages are passed using the
1190 system calls, using a
1202 Returns any non-generic messages as their own response.
1233 Encapsulates/de-encapsulates frames encoded according to RFC 1490.
1239 Encapsulates/de-encapsulates Frame Relay frames.
1261 This node encapsulates and de-encapsulates asynchronous frames
1266 This node is attached to every Ethernet interface in the system.
1270 This node is also a system networking interface.
1279 This node implements a simple round-robin multiplexer.
1289 capacity PPP system.
1303 bridging system to be implemented.
1305 This intriguing node looks like a socket to the system but diverts
1308 system for further processing.
1316 Whether a named node exists can be checked by trying to send a control message
1331 .Bl -enum
1345 Both control messages and data are delivered and queued with a
1353 .Bl -tag -width indent
1386 There is a library for supporting user-mode programs that wish
1389 system.
1394 Two user-mode support programs,
1401 First, implementing new node types in user-mode first
1465 system was designed and first implemented at Whistle Communications, Inc.\&
1472 .An -nosplit