CN100428171C - Communication method between data plane and control plane - Google Patents

Abstract

The invention relates to a communication method between a data plane and a control plane, comprising the following steps: when a user space application program running on an operating system of the control plane sends data to a first pseudo-device registered in the operating system running on the control plane , the first pseudo-device copies the data to the kernel space of the operating system running on the control plane; if the data plane runs on a multi-core system, the data is sent from the kernel space to the second pseudo-device registered in the multi-core system; if If the data plane runs on a single-core system, the second pseudo-device directly reads data from the kernel space. Pseudo devices with consistent interfaces are registered on the data plane and control plane respectively, and the judgment of the hardware environment and the operation of multi-core hardware and inter-core communication are encapsulated, so that the design of the upper-layer business module does not need to consider the hardware environment, thereby enhancing the upper-layer Adaptability and scalability of business modules.

Description

Communication method between data plane and control plane

technical field

The invention relates to a communication method between a data plane and a control plane in a data communication device, especially for performing data communication between the data plane and the control plane when an upper-layer application program is executed in a multi-core (Multi-Core) environment method.

Background technique

Data communication equipment (equipment used for data communication, such as routers, etc.) can generally be logically divided into two parts: data plane (DATA PLANE) and control plane (CONTROL PLANE) according to different job functions. High-speed processing of messages, while the control plane mainly runs management software, which is responsible for configuring the entire system and running some control layer protocols.

In a general single-core (Single-Core) system, the data plane and the control plane are not physically separated structures. They share a CPU and alternately obtain CPU time to run their programs. Taking a datacom device using Linux as an operating system as an example, it is assumed that the control plane runs in the user space of Linux, and the data plane runs in the kernel space of Linux. Since the memory of Linux user space and kernel space are isolated from each other, when the hypervisor running on the Linux control plane interacts with the program of the data plane, it must be realized through the communication between the user space and the kernel space. In fact, user space and kernel space are only logically isolated in the operating system, and they can share a memory space. Therefore, the data plane and the control plane generally use shared memory to communicate.

The emergence of multi-core CPU provides good conditions for the data plane and control plane to run with higher efficiency. In the multi-core system design, it can be divided into two categories according to the different processing functions of each core (Core) in the multi-core CPU, one of which runs the operating system and applications on the data plane, and the other runs the operating system and applications on the control plane. program.

According to this classification method, you can choose to run the control plane system and program on one core of the multi-core CPU. The control plane uses the Linux operating system to provide a general and open management configuration platform; the data plane system and program run on other cores. , running dedicated systems and programs related to applications on the data plane. The data plane system and the control plane system have a shared physical memory.

This division of labor can obviously improve data processing efficiency, but since the two planes run on different cores and logically use different memory spaces, they can be regarded as two devices. Such a system design method must consider the communication mode of the data plane and the control plane based on the multi-core CPU.

The existing multi-core CPU provides an inter-core high-speed communication path API (i.e., an inter-core high-speed communication path realized by the multi-core CPU hardware). The basis for communication between cores running the data plane and cores running the control plane. However, for the transmission of a large amount of data between cores, a high-speed communication path between cores combined with shared memory is required.

Although the above-mentioned technical solution solves the communication problem between the data plane and the control plane in the multi-core CPU environment, the application program interface of the bottom layer lacks encapsulation. API to control, in the program design must consider the situation of the underlying hardware and design the corresponding processing method, it is difficult to achieve hardware independence, the design is difficult, and it is not easy to transplant.

Contents of the invention

The purpose of the present invention is to propose a communication method between the data plane and the control plane, so that the upper layer business modules of the data plane or the control plane do not need to consider the underlying hardware differences when designing, and are applicable to both multi-core environments and single-core environment.

In order to achieve the above object, the present invention provides a communication method between a data plane and a control plane, comprising the following steps:

When a user space application running on the operating system on the control plane sends data to a first pseudo-device registered in the operating system running on the control plane, the first pseudo-device copies the data to the operating system running on the control plane The kernel space of the system;

If the first pseudo-device judges whether the data plane runs on multi-core system hardware, if yes, it sends data from the kernel space to the second pseudo-device registered in the multi-core system data plane running on the data plane.

In the above technical solution, if the data plane runs on a single-core system, otherwise, the second dummy device directly reads data from the kernel space.

The pseudo-device encapsulates the underlying operations of the hardware, and can transmit data according to the hardware environment of single-core hardware and multi-core hardware. When the upper-layer application calls the pseudo-device to communicate between the data plane and the control plane, it does not need to consider the underlying communication implementation. The method reduces the difficulty of application program design and realizes portability on single-core hardware and multi-core hardware.

When the data sent by the user space application to the first pseudo-device is an operation instruction, the operation of sending the data from the kernel space to the second pseudo-device registered in the operating system running on the data plane is specifically:

Encapsulating the device information of the first pseudo-device and the operation instruction into a message, and sending the message from the kernel space to an operating system running on a data plane through an inter-core high-speed communication channel;

The operating system running on the data plane parses out the device information and operation instructions of the first pseudo-device in the message, searches for the corresponding second pseudo-device according to the device information, and then provides the operation instruction to the second pseudo-device so that the second pseudo-device performs a corresponding operation.

If the data interacted between the control plane and the data plane is configuration information for configuring the data plane, the operation of sending the data from the kernel space to the second pseudo-device registered in the data plane of the multi-core system is specifically:

The inter-core high-speed communication channel is called to send the configuration information from the kernel space to the multi-core system, and the multi-core system configures the second pseudo-device according to the configuration information.

In addition to the encapsulation of multi-core hardware and single-core hardware, encapsulation can also be performed on the data transmission mode between the control plane and the data plane, and the data is sent from the kernel space to the multi-core system registered in the data plane. The operation of the second pseudo-device is specifically: the first pseudo-device judges whether the data is lower than the preset capacity threshold, and if so, encapsulates the data into a message, and sends the to the CPU core where the data plane of the multi-core system is located; otherwise, the CPU core where the kernel space is located writes the data into the shared memory, and encapsulates the memory address of the data into a message, and sends it to the multi-core through the inter-core high-speed communication channel The CPU core where the system data plane is located, and then the CPU core where the multi-core system is located fetches data from the shared memory according to the memory address in the message.

The inter-core high-speed communication path is suitable for the high-speed transmission of a small amount of data between the cores. When the amount of data to be transmitted between the cores is large, it is necessary to combine the inter-core high-speed communication path and shared memory to realize the inter-core data transmission. When the respective operating systems of the data plane and the control plane are initialized, the shared memory area can be mapped to a memory block at the same physical address. This memory block is independent from the respective operating systems. At this time, the two plane systems are Access to shared memory is possible. During communication, the CPU core as the sender writes the data that needs to be interacted into the shared memory, encapsulates the memory address in the message of the inter-core high-speed communication channel, and sends the message to the CPU core as the destination. After parsing the received message, the CPU as the destination takes out the data from the shared memory according to the physical address in the message.

Further, when the data plane runs in a single-core environment, the user space and the kernel space are in the same CPU core, so the second pseudo-device can directly access the shared memory of the kernel space of the operating system running on the control plane, and read data.

When registering the first pseudo-device and the second pseudo-device, setting a consistent operation interface for the first pseudo-device and the second pseudo-device can greatly simplify the design difficulty of the upper layer program.

When setting the operation interface for the first pseudo-device and the second pseudo-device, a consistent character-type device operation interface can be set, and the operation of the character-type device includes opening the pseudo-device, closing the pseudo-device, reading data from the pseudo-device, One or more operations in which the device writes data, sends operation instructions to the pseudo-device, and reads status information from the pseudo-device.

It is also possible to set a consistent network operation interface, when registering the second pseudo-device in the operating system running on the data plane, assign an IP address to the data plane, and add it to the data plane in the operating system running on the control plane communication routing table. The network device method adopted can encapsulate the second pseudo-device and the shared memory and inter-core high-speed communication channel used in the communication of the second pseudo-device into one network device, so that the interaction between the control plane and the data plane can be regarded as two Interaction between network devices, this interaction uses TCP/IP protocol, and realizes communication through Socket (socket). Due to the popularity of the TCP/IP protocol, this method has strong scalability and adaptability.

Based on the above technical scheme, the present invention has the following advantages:

1. The present invention uses pseudo-device for data transmission on the data plane and control plane. The pseudo-device encapsulates the judgment of the hardware environment and the operation of inter-core communication specific to multi-core hardware, so that the design of the upper-layer business module does not need to consider the hardware environment. , thus enhancing the adaptability and scalability of the upper layer business modules.

2. The present invention designs the pseudo-device management method for the applicable device management method in the operating system to make it easy to be compatible. The character device or block device management method can be used in the design, and the network management method can also be used, so it also has a comparative advantage. Great flexibility.

3. The present invention provides a unified operation interface for upper-layer application programs under different hardware environments, which greatly simplifies the design of upper-layer application programs.

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

Description of drawings

FIG. 1 is a schematic diagram of the structure of the present invention applied in a single-core environment.

FIG. 2 is a schematic diagram of the structure of the present invention applied in a multi-core environment.

FIG. 3 is a schematic flowchart of an embodiment of a communication method between a data plane and a control plane according to the present invention.

FIG. 4 is a schematic flowchart of another embodiment of the communication method between the data plane and the control plane of the present invention.

FIG. 5 is a schematic flowchart of another embodiment of the communication method between the data plane and the control plane of the present invention.

Detailed ways

The principle of the present invention is to use the pseudo-device registered in the operating system to complete the data communication between the data plane and the control plane, and the pseudo-device encapsulates the adaptation process to the hardware environment and/or data transmission mode. The interface of the device adopts a unified interface, which greatly simplifies the design of the upper layer application program, and does not have to consider the impact caused by its hardware environment.

As shown in FIG. 1 , it is a schematic diagram of the structure of the present invention applied in a single-core environment. An operating system is run in a single-core CPU, and the operating system includes user space and kernel space. The user space and kernel space represent different operating states of the operating system. The data plane runs in the kernel space, and the control plane runs in the user space. There is a control plane application 1 running in the user space, which can operate on the data plane application 2 in the data plane. The data plane application 2 interacts with the control plane application 1. When the system starts, it will be in the user space Register pseudo-device 3 and pseudo-device 4 respectively with the kernel space. The interface definitions of pseudo-device 3 and pseudo-device 4 must be set to be consistent. The data interaction between pseudo-device 3 and pseudo-device 4 is realized through shared memory.

For a multi-core environment, as shown in FIG. 2 , a schematic structural diagram of the present invention applied in a multi-core environment. The control plane runs on the control plane CPU, the operating system runs on the control plane, and the data plane runs on the data plane CPU. The data plane CPU is a core different from the control plane CPU, and runs dedicated operations in the data plane. Systems and programs, such as some dedicated embedded systems. The control plane application 1 runs in the control plane, and can operate the data plane application 2 on the data plane, and the data plane application 2 and the control plane application 1 perform data interaction. When the system starts, register the pseudo-device 3' in the control plane, and register the pseudo-device 4' in the data plane. Like the single-core environment, its interface definition can be consistent with the pseudo-device 3'.

The basic process of the present invention is shown in Figure 3, which is a schematic flow diagram of an embodiment of the communication method between the data plane and the control plane of the present invention, including the following steps:

Step 101, when the user space application program running on the operating system of the control plane sends data to the first pseudo-device registered in the operating system running on the control plane, the first pseudo-device copies the data to the The kernel space of the flat operating system;

Step 102, if the data plane runs on a multi-core system, execute step 103; if it runs on a single-core system, execute step 104;

Step 103, sending data from the kernel space to the second pseudo-device registered in the multi-core system, and ending the operation;

In step 104, the second dummy device directly reads data from the kernel space.

When designing pseudo-device, different program structures can be realized through macros for multi-core systems or single-core systems. When compiling pseudo-device programs for multi-core systems or single-core systems, select the corresponding macros for multi-core systems or single-core systems. Perform a compile operation. The compiled pseudo-device program can provide an upper-layer application interface for the multi-core system or single-core system, so that the upper-layer application program does not need to implement a corresponding program framework for the multi-core system or single-core system, thereby simplifying the program design.

When the datacom device is started, the operation of registering the pseudo-device will be performed, and the operation interface consistent with that of the first pseudo-device can be set for the second pseudo-device during the registration process. In this way, the design difficulty of the upper-layer application program can be reduced, and the upper-layer application program has good portability. When performing data interaction between the kernel space and the data plane, it is also necessary to judge the hardware environment to select different processing procedures.

When the data communication device is a multi-core hardware environment, the pseudo-device can use the inter-core high-speed communication path to transmit data. Please refer to FIG. 4, which is a schematic flow diagram of another embodiment of the communication method between the data plane and the control plane of the present invention , including the following steps:

Step 101, when the user space application program running on the operating system of the control plane sends data to the first pseudo-device registered in the operating system running on the control plane, the first pseudo-device copies the data to the The kernel space of the flat operating system;

Step 102, if the data plane runs on a multi-core system, then execute step 103a; if the data plane runs on a single-core system, then execute step 104';

Step 103a, encapsulating the device information and operation instructions of the first pseudo-device into a message, and sending the message from the kernel space to the operating system running on the data plane;

Step 103b, parsing out the device information and operating instructions of the first pseudo-device in the message, searching for a second pseudo-device corresponding to the device information, operating according to the operating instructions, and then ending the operation;

Step 104', the second pseudo-device directly accesses the shared memory in the kernel space of the operating system running on the control plane, and reads data.

Since the device information of the second pseudo-device has been registered in the data plane, after receiving the message, the device information of the first pseudo-device (which can be pseudo-device name, device parameters, etc.) can be found out correspondingly. pseudo-device, and the second pseudo-device performs corresponding operations according to the operation instructions. In a single-core environment, since the control plane and the data plane are actually in different operating states of the same operating system, the second pseudo-device can directly read data, and execute corresponding operations if the data is a certain operation instruction.

Pseudo-devices can be used under various operating systems running on the control plane, such as FreeBSD, Solaris, and Linux. The following takes Linux as an example to provide an example of the interface definition of a pseudo-device. Here, the C language is used as an example.

In Linux, register_chrdev(unsigned int major, const char*name, struct file_operations*fops) and unregister_chrdev(unsignedint major, const char*name) define the registration and unloading interface of the pseudo-device, where constchar*name is the registration name of the pseudo-device, It is the name that needs to be specified when the Linux user mode program accesses the device, and then the operation interface can be selected as required, such as selecting the character device operation interface and the network operation interface.

First take the character device operation interface as an example, the character device operations can include: open the pseudo device (open), close the pseudo device (close), read data from the pseudo device (read), write data to the pseudo device (write ), sending operation instructions to the pseudo-device and reading status information (ioctl) from the pseudo-device. Before performing operations on the pseudo-device, the operation of opening the pseudo-device needs to be performed first.

This character-type device operation interface is used when the pseudo-device adopts the character device mode or the block device mode, and these two device management modes are consistent with the device management mode in Linux.

The present invention also provides another device management mode of pseudo-device: network device mode. The operation interface it adopts is a network operation interface. Compared with the character-type device operation interface, in addition to operations such as opening and closing, it needs to perform data interactive transmission through sockets. When registering the second pseudo-device in the operating system running on the data plane, it is necessary to allocate an IP address for the data plane, and add to the communication routing table of the data plane in the operating system running on the control plane.

The following describes in detail the interface for sending operation instructions to the pseudo-device and reading status information (Ioctl) from the pseudo-device in the character-type device operation interface. This interface can configure the device and complete the command and data interaction between the control plane and the data plane.

When the data sent by the application program in the user space to the first pseudo-device is the configuration information used to configure the data plane, the Ioctl interface can be used to operate. First, the first pseudo-device copies the configuration information to the operating system running on the control plane. kernel space; if the data plane runs in a multi-core system, call the inter-core high-speed communication channel to encapsulate the configuration information, and send it from the kernel space to the multi-core system, and the multi-core system configures the second pseudo-device according to the configuration information; If the data plane runs on a single-core system, the second pseudo-device directly reads the configuration information from the kernel space and performs a configuration operation. After configuration, you can choose whether to return information to user space according to your needs.

For a multi-core system, the operating system running on the control plane encapsulates the Ioctl operation instruction into a specified message format, and then calls the multi-core inter-core high-speed channel to send it to the core where the data plane is located for processing. After the processing is completed, the core where the data plane is located encapsulates the return value in a message, sends it back to the core where the control plane is located, and then returns the result to the user space application according to the content of the response message.

The format of the message is given below in C language, and the format of the message provided by the present invention is only an example, and is not intended as a limitation on the format of the message.

struct ioctl_msg

{

  unsigned short tunnel_id; /*Receive message queue ID*/

unsigned long addr; /*ioctl command content address pointer*/

  chardev_name[DEV_NAME_LEN_MAX]; /*pseudo-device name*/

unsigned int ioctl_cmd; /*ioctl command number*/

  int ret; /*ioctl execution result return value*/

};

The above examples are all implemented in C language, but this does not limit the implementation language of the present invention to C language, and other high-level languages or assembly languages that can realize pseudo-device should be covered by the present invention.

The communication process based on the above message format is given below. The first pseudo-device first takes out the length of the buffer area issued by Ioctl from the command number, and applies for a piece of shared memory. When the configuration is issued, the ioctl is issued from the user space. Copy the contents of the buffer to the shared memory; then encapsulate the ioctl command number, the pseudo-device name and the physical address of the shared memory into the message format, and send the message; after the operating system running on the data plane finds the second pseudo-device, The second pseudo-device encapsulates the response message receiving queue into a message format, receives the response message from the response receiving queue, and then extracts the ioctl return code from the message. When the ioctl command reads the configuration, the address of the Ioctl output buffer is taken out from the message and the content in the shared memory is written back to the user space, then the shared memory is released, and the return code is returned.

If the upper-layer business modules running on the data plane do not need to consider the influence of the hardware when interacting with the control plane applications in the control plane, this upper-layer business module can run in a dedicated embedded system to embed For example, when the system is started, it is necessary to register a pseudo-device that is consistent with the interface of the pseudo-device in the operating system running on the control plane. The implementation method of C is still used as an example, as follows:

In addition to the definition of registration and uninstallation interfaces, it is also necessary to realize the management of pseudo-device in the embedded system of multi-core system and save the registration information of pseudo-device. After the embedded system receives the message, it parses, searches for the registered pseudo-device according to the device name of the pseudo-device in the parsed message, and executes the registered operation of the pseudo-device. After the embedded system finishes processing the rpc_ioctl command, it needs to encapsulate the return value and the address of the output buffer into the above message format, and send the message back to the core where the control plane of the multi-core system is located through the message ring. It has been described above that the pseudo-device encapsulates the hardware impact of the multi-core environment and the single-core environment. The method of message transmission in the multi-core environment can be further encapsulated, as shown in FIG. 5, which is another communication method between the data plane and the control plane of the present invention. A schematic flow chart of an embodiment includes the following steps:

Step 101, when the user space application program running on the operating system of the control plane sends data to the first pseudo-device registered in the operating system running on the control plane, the first pseudo-device copies the data to the The kernel space of the flat operating system;

Step 102, the first dummy device judges whether the data plane runs on multi-core hardware, if it runs on multi-core hardware, then executes step 1031, if it runs on single-core hardware, then executes step 104';

Step 1031, the first dummy device judges whether the transmitted data is lower than the preset capacity threshold, if yes, execute step 1035, otherwise execute step 1032;

Step 1032, the CPU core where the kernel space is located writes data into the shared memory;

Step 1033, encapsulate the memory address of the data into a message, and send it to the CPU core where the operating system running on the data plane is located through the inter-core high-speed communication channel;

Step 1034, the CPU core where the operating system running on the data plane is located takes the data out of the shared memory according to the memory address in the message, and ends the operation;

In step 1035, the data is encapsulated into a message, and the CPU core where the kernel space is located is sent to the CPU core where the operating system running on the data plane is located via the inter-core high-speed communication channel, and the operation is terminated;

Step 104', the second pseudo-device directly accesses the shared memory in the kernel space of the operating system running on the control plane, and reads data.

This embodiment provides further encapsulation of data transmission between the control plane and the data plane, that is, a combination of inter-core high-speed communication channel and shared memory is adopted, wherein the inter-core high-speed communication channel uses messages to transmit data, and messages usually require Encapsulates the identifying flag of the pseudo-device. As described in this embodiment, the messages transmitted on the inter-core high-speed communication channel can only transport a small amount of data. If a large amount of data needs to be transmitted, it is necessary to use the shared memory method. At this time, the function of the message is to transmit The physical address where the data resides.

It can be seen from the above specific process that the upper-layer business modules and application programs only need to use a unified program interface for design, and do not need to consider the complex hardware environment. The adaptation of the hardware environment and communication methods is done by the pseudo-device From the perspective of user design and use, the influence of hardware is shielded, thus reducing the difficulty of design. Since various pseudo-devices can adopt a unified interface, the upper-layer business module also has good scalability and portability.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them; although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that: the present invention can still be Modifications to the specific implementation of the invention or equivalent replacement of some technical features; without departing from the spirit of the technical solution of the present invention, should be included in the scope of the technical solution claimed in the present invention.

Claims (10)

1. A communication method between a data plane and a control plane, comprising the following steps: When a user space application running on the operating system on the control plane sends data to a first pseudo-device registered in the operating system running on the control plane, the first pseudo-device copies the data to the operating system running on the control plane The kernel space of the system; If the data plane runs on a multi-core system, sending data from the kernel space to a second dummy device registered in the data plane of the multi-core system. 2. The communication method between the data plane and the control plane according to claim 1, wherein if the data plane runs on a single-core system, the second dummy device reads directly from the kernel space fetch data. 3. The communication method between the data plane and the control plane according to claim 1, wherein when the data sent by the user space application program to the first pseudo-device is an operation instruction, the data is sent from the The operation of sending the kernel space to the second pseudo-device registered in the data plane of the multi-core system is as follows: Encapsulating the device information of the first pseudo-device and the operation instruction into a message, and sending the message from the kernel space to the multi-core system through an inter-core high-speed communication channel; The multi-core system parses out the device information and operation instructions of the first pseudo-device in the message, searches for the corresponding second pseudo-device according to the device information, and then provides the second pseudo-device with the operation instruction to make the second pseudo-device The pseudo-device performs the corresponding operation. 4. The communication method between the data plane and the control plane according to claim 1, wherein when the data sent by the user space application to the first dummy device is configuration information for configuring the data plane, the The operation of sending data from the kernel space to the second pseudo-device registered in the data plane of the multi-core system is as follows: The inter-core high-speed communication channel is called to send the configuration information from the kernel space to the multi-core system, and the multi-core system configures the second pseudo-device according to the configuration information. 5. The communication method between the data plane and the control plane according to claim 1, characterized in that the operation of sending data from the kernel space to the second pseudo-device registered in the data plane of the multi-core system Specifically: the first pseudo-device judges whether the data is lower than the preset capacity threshold, and if so, encapsulates the data into a message, and sends the data to the multi-core system through the CPU core where the kernel space is located via the inter-core high-speed communication channel The CPU core where the plane is located; otherwise, the CPU core where the kernel space is located writes data into the shared memory, and encapsulates the memory address of the data into a message, and sends it to the CPU core where the data plane of the multi-core system is located through the inter-core high-speed communication channel , and then the CPU core where the data plane of the multi-core system is located fetches the data from the shared memory according to the memory address in the message. 6. The communication method between the data plane and the control plane according to claim 2, wherein the operation of directly reading data from the kernel space by the second pseudo-device is specifically: The second pseudo-device directly accesses the shared memory in the kernel space of the operating system running on the control plane, and reads data. 7. The communication method between the data plane and the control plane according to any one of claims 1-6, wherein when registering the first pseudo-device and the second pseudo-device, the first pseudo-device and the second pseudo-device The two pseudo devices set the same operation interface. 8. The communication method between the data plane and the control plane according to claim 7, wherein the operation of setting a consistent operation interface for the first pseudo-device and the second pseudo-device is specifically: Set a consistent character device operation interface for the first pseudo device and the second pseudo device, and the character device operations include opening the pseudo device, closing the pseudo device, reading data from the pseudo device, writing data to the pseudo device, and writing data to the pseudo device. One or more operations of sending operation instructions from the pseudo-device and reading status information from the pseudo-device. 9. The communication method between the data plane and the control plane according to claim 7, characterized in that the operation of setting a consistent operation interface for the first pseudo-device and the second pseudo-device is specifically: for the first pseudo-device The first pseudo-device and the second pseudo-device set the same network operation interface. 10. The communication method between the data plane and the control plane according to claim 9, characterized in that when registering the second pseudo-device in the data plane of the multi-core system, an IP address is assigned to the data plane, and the The operating system running on the control plane is added to the communication routing table of the data plane.

Images