KR0146025B1 - Board driving apparatus of fiber distributed data interface using stream mechanism on the unix system - Google Patents

Abstract

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a fiber distributed data interface (hereinafter referred to as FDDI) board drive, and more particularly, to a UNIX system kernel using a standard stream mechanism to facilitate data transfer between systems. The FDDI board driving apparatus using the stream method, the FDDI board driving apparatus of the present invention is implemented in the Unix system kernel (SVR4.0), a RAM device for transmitting data in character units between the application program and the FDDI board in the system It consists of a driver and a network interface driver that performs data transmission and reception between systems while interacting with TCP / IP modules in the Unix kernel in the form of stream message data.

Description

Fiber Distribution Data Interface (FDDI) Board Driver Using Stream Method in UNIX System Kernel

1 is a block diagram showing the relationship between the FDDI board driver and the adjacent modules according to the present invention.

2 is a block diagram showing functions constituting a RAM driver module according to the present invention.

3 is a flowchart illustrating an initialization process of the FDDI board driver according to the present invention.

4 is a flowchart illustrating a process of performing downloading using a RAM driver module according to the present invention.

5 is an internal block diagram of a network interface driver according to an embodiment of the present invention.

6 is an operational flowchart of a write foot procedure according to the present invention.

7 is an FDDI frame format diagram implemented according to the American National Standards Institute (ANSI) X3T 9.5 standard.

8 is an explanatory diagram showing a ring driving sequence;

9 is a block diagram illustrating address mapping between a virtual address of a network interface driver and an address of an FDDI board according to the present invention.

FIG. 10 is a flowchart illustrating a process in which the FDDI board driver according to the present invention transfers data received from a communication network to a driver of a host.

* Explanation of symbols for main parts of the drawings

10: RAM device driver 11: Host SMT driver

20: network interface driver

30: Stream device driver (TCP / IP protocol)

40: FDDI board 50: Downloading program

60: SMT control program

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fiber distributed data interface (hereinafter referred to as FDDI) board drive, and more particularly, to a UNIX system kernel using a standard stream mechanism to facilitate data transfer between systems. The present invention relates to an FDDI board driving apparatus using a stream method.

In general, the FDDI driver is located between the FDDI board and the communication protocol using the FDDI communication network to control the operation of the FDDI board, and also transmits data from the host to the FDDI board or receives data from the FDDI board in the host communication protocol. It is responsible for the function of transmitting to the data, and is used to provide smooth data transmission and control of the FDDI board.

In particular, the standard of the FDDI board according to the American National Standards Institute (ASC X3T9.5) recommendation of ANSI (American National Standard Institute) is a communication network protocol that transmits data at high speed using optical fiber as a communication medium, and transmits up to 100MBit / sec. It is a protocol that has a speed, the maximum communication distance between nodes is 2Km, and the physical connection to the FDDI communication network is 100Km at maximum.

These existing device drivers for FDDI have been implemented as character device driver types to run on BSD versions or SunOS versions.

On the other hand, V version (SVR4.0), a new version of Unix system, provides a stream mechanism in which network protocols and device drivers are implemented differently from the conventional BSD version or SunOS version. Implemented as

Therefore, in the system V version (SVR4.0) of the Unix system, since the existing FDDI device driver cannot be used to transmit information between systems, a communication protocol implemented using the stream mechanism of the system V version of the Unix system (TCP). For the interworking between / IP), a device driver with a stream mechanism is required.

The present invention is to provide an FDDI board driving apparatus using the stream method in the Unix (UNIX) system kernel that can be interconnected with the upper protocol TCP / IP using the stream scheme provided by the Unix kernel by this necessity do.

The FDDI board driving apparatus of the present invention for achieving the above object is implemented in the Unix system kernel (SVR 4.0), a RAM device driver for transmitting data in character units between the application program and the FDDI board in the system, the Unix kernel It consists of a network interface driver that performs data transmission and reception between systems while interacting with TCP / IP modules in the form of stream message data.

Hereinafter, a preferred embodiment of a fiber distribution data interface (FDDI) board driving apparatus using a stream method in a UNIX system kernel according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing the relationship between the FDDI board drive device and the adjacent modules according to the present invention, as shown in the figure, the FDDI board drive device existing in the kernel area and the protocol or application program associated therewith in the user area. A reference drawing describing the relationship between them.

Referring to FIG. 1, the FDDI board driver, that is, a device driver, of the present invention in the kernel region includes a RAM device driver (i.e., a character device driver) 10 and a network interface driver (i.e., a stream device driver) ( 20)

At this time, the RAM device driver 10 is an application program (such as a download program 50 or a state information access (hereinafter referred to as SMT) control program 60, etc.) of the user area directly call the name of the device FDDI board ( 40) to download data or to read the information of the FDDI board 40, to control the SMT protocol of the FDDI board 40 or to read the SMT-related information from the board, the device of the It is used when the destination of data that any application program (downloading program 50 or SMT control program 60) wants to send or receive is not the state machine but the memory of FDDI board of kernel area. In this case, device driver Does not need to use the kernel's communication protocol, only the function of passing data to the designated area of the FDDI board. to be.

Meanwhile, the network interface driver 20 stores data handled by the network interface driver 20 in order to interoperate with the TCP / IP protocol module 30 which is a higher module in the Unix kernel. It is composed of stream messages by the stream mechanism provided by the network), and the data of a plurality of application (FTP, TELNET, SMTP, SNMP, NFS) data of the TCP / IP communication protocol that performs the TCP / IP stream module 30 It allocates to the write queue of the driver 20 in a waiting state.

FIG. 2 is a reference diagram showing related functions of a RAM device driver according to the present invention. Referring to FIG. 2, related functions of the RAM device driver may include an initialization function (CLEAR), an open function (OPEN), and a closure function (CLOSE). ), Read function (READ), write function (WRITE), input / output control function (IOCTL), and interrupt processing function (ITRT). It is similar to general character device driver.

The read function READ and write function WRITE of the RAM device driver 10 use a uio data structure and a uiomove function provided by a kernel region of a Unix system for use in data transfer between a user and a kernel. The I / O control function (IOCTL) is used for requesting status information of a board or specifying an arbitrary variable value by a user or an application program using an FDDI board. The function provided by the input / output control function may be divided into a function of specifying or retrieving a part related to operating the board and a value of the host SMT driver 11 of the FDDI board.

FIG. 3 is a flowchart illustrating an initialization process performed by a Unix system with respect to the FDDI board driver according to the present invention. Referring to FIG. 3, the operation of the initialization function for initializing the FDDI board driver is first performed by the system. If it is not initialized by checking whether it is initialized (S31), the number of FDDI boards attached to the system is checked (S32), and then the control structures are allocated as many as the checked number (S33). Each VME area is allocated (S34). Then, it is checked whether the allocated VME area is available (S35), and if it is available (preliminary branch of S35), the initial address of the corresponding VME area per board is assigned to the corresponding control structure (S37), and each control structure is assigned. Control of interrupt vector, board sequence number, debug flag, status information of each board, board type, interrupt and reset window size of each board, data transfer buffer, data receive buffer, data frame size, frame header size and DMA status information The information is specified (S38).

FIG. 4 is a flowchart illustrating a process of downloading data of a user area to a memory of an FDDI board by using a RAM driver module according to the present invention. Referring to FIG. 4, the downloading process is first performed by using a RAM device. Open the driver (S41) and reset the FDDI board (S42). After setting the relevant flag at the time of transmission and reception (S43) and opening the file to be downloaded (S44), one record of the downloading file is stored in a buffer and a data error of the record is retrieved, and a syntax error of the record is obtained. Search (S45) to download to the FDDI board through the VME area (S46) and then finish (S47).

Typical application programs using the RAM device driver 10 as described above include a downloading program 50 for downloading data of a user area into a memory of an FDDI board and accessing status information for searching or specifying a state of the FDDI board. SMT) program 60.

FIG. 5 is an internal block diagram of a network interface driver according to an embodiment of the present invention. Referring to FIG. 5, the network interface driver provided by the present invention receives a message from a TCP / IP module, which is an upper module. A write foot procedure 51 for determining the type of a message, and when a message is received by the write foot procedure 51, sets a driver corresponding to the message and transmits the message to the write foot procedure 51. The driver setting manager 52 and the FDDI frame header are added to configure the received message as a frame, and then received from the frame constructor 53 for transmitting to the write foot procedure 51 and the write foot procedure 51. A write service procedure 54 for controlling a written message to be written to an FDDI board, and under the control of the write service procedure 54, an FDDI is controlled. A write ring manager 55 for writing messages to the network, a stream scheduler 56 for temporarily storing messages in the form of streams to be read or written through the network interface driver, and a read ring manager for reading messages from the FDDI board. 58), an interrupt handler 57 for recognizing the fact that a message is transmitted from the read ring manager 58 through an interrupt, and a read service for controlling a message read from the FDDI board to be transmitted to the upper module TCP / IP module. It consists of a procedure 59.

FIG. 6 is a flowchart illustrating an operation of a write foot procedure according to an embodiment of the present invention for transmitting data to an FDDI communication network. Referring to FIG. 6, the write foot procedure first determines a data type of a stream message (S51) and types of data. It is executed independently according to (M_PROTO, M_PCPROTO, M_IOCTL, M_FLUSH) and does not have a return value for the processing result.

As such, the data types processed by the write foot procedure based on the determination of the data type include M_PROTO, M_PCPROTO, M_IOCTL, and M_FLUSH for flushing the read / write queue, and, if so, enter the write queue of the network interface driver 20. If the data type of the message is M_IOCTL (S51 M_IOCTL branch), if it is an input / output data structure (ioblk) after checking whether the contents of the stream message are an input / output structure (ioblk) data structure (S52). Search the ioc-uid and ioc-count fields of the input / output data structure (ioblk) (s53), analyze the command value (ioc_cmd) (s54), and if the value is GETADDR, enter the data area of the input / output control structure. The physical address of the board is recorded and sent to the read queue of the upper stream module (S55). Information about these physical addresses is managed in a routing table, and the ARP / RARP (Address Resolution Protocol / Reverse Address Resolution Protocol) module By is used.

In addition, when the command (ioc-cmd) value is specified to terminate the operation of the network interface driver, it changes to terminate the information related to the operation status of the network interface driver and the FDDI board. In this case, after performing the corresponding operation, a message having information on the result is constructed and transmitted to the read queue of the upper module (S61).

If the data type of the message passed to the write put procedure is M_PROTO or M_PCPROTO (M_PROTO M_PCPROTO branch in S51), the stream message consists of a DL_raw structure (S62), and the raw fields of the structure (DL_BIND_REQ, DL_UNBIND_REQ, DL_INFO_REQ DL_UNITDATA_REQ). It consists of a DL_BIND_REQ primitive structure, a DL_UNBIND_REQ primitive structure, a DL_INFO_REQ primitive structure, and a DL_UNITDATA_REQ primitive structure.

In case of DL_BIND_REQ primitive structure, the network interface driver is connected to the stream link before the actual data transferred from the upper module to the FDDI board (s63), so that the read / write queue of the upper stream module and the read / write queue of the network interface driver are respectively. It is a primitive structure that requests to be interconnected. It is called by the kernel when all the modules registered in the stream's configuration file are connected to the stream link at system boot time. The driver uses the FDDI's physical address size, The included DL_BIND_ACK is configured as a stream message (S63 to S64) and delivered to the read queue of the upper module (S69).

The DL_UNBIND_REQ primitive structure is used when a stream link is requested to remove a network interface driver. The DL_UNBIND_REQ primitive structure is composed of a DL_OK_ACK primitive structure, changed to a stream message (S65 to S66), and transferred to a read queue of a higher module (S69).

In case of DL_INFO_REQ primitive structure, the primitive structure used when the upper module wants to obtain information about the driver before passing data between the network interface driver and the upper module. The driver serving as an information provider has information about the frame and driver status. Information and information related to qos are recorded in the DL_INFO_ACK primitive structure to construct a stream message (S67 to S68), and then transferred to the read queue of the upper module (S69).

The above-mentioned DL_BIND_REQ and DL_INFO_REQ primitive structures are preprocessing procedures that are performed to smoothly send and receive data before transmitting stream data containing data of an actual application service to a board.

In the present invention, the data transmitted from the TCP / IP module is transmitted to the FDDI board by using the DL_UNITDATA raw structure without using the M_DATA message type to send the data to the board.

Looking at the data transmission procedure, first, if the destination of the stream message is a loopback, the DL_UNIDATA_IND primitive structure is reconstructed and transferred to the read queue of the higher order module.

If the destination of the message is broadcast, one message is delivered to the upper module in the same procedure as loopback for local, and the destination address is designated as the broadcast address (0xffffffff).

The most important function here is to construct an FDDI header, followed by the actual data to form a frame.

FIG. 7 is a schematic diagram of an FDDI frame format implemented according to the American National Standards Institute (ANSI) X3T9.5 standard. As shown in the drawing, a preamble bit, a start designation modifier (SD), and a frame control field (FC) FDDI frame, which is composed of destination address (DA), source address (SA), data field (INFO), frame check order (FCS), end designation qualifier (ED), and frame status indication bit (FS). The first part of the data field (INFO) of the frame is a 3 byte LLC header (DSAP, SSAP, CONTROL) and a 5 byte SNAP header (protocol ID or org code and packet type) according to the FDDI standard. Is assigned, followed by the data.

Therefore, the header part of the write foot procedure is assigned the DSAP and SSAP fields of the LLC header and the org code and the sap number of the SNAP header according to the RFC1390 recommendation proposed by the US Department of Defense. The sap value is 0x0800 indicating the sap of the IP module. And 0x0806 indicating the ARP module. In addition, the destination address (DA) field, which is the physical address of the destination, and the physical address of the FDDI transmitted from the board by the M_IOCTL message, are written to the SA, which is the physical address of the sending board. do.

The stream message composed of one frame by the write put procedure is allocated to the write queue of the network interface driver 20 and waits for processing by the write service procedure.

When control is passed to the write service procedure of the network interface driver 20 by the stream scheduler, the stream messages, which are already configured by the write service procedure and are waiting in the write queue, are delivered to the FDDI board one by one. The message is taken and delivered to the buffer memory of the FDDI through the VMEbus. When the status of the network interface driver 20 and the status of the FDDI board are abnormal or the buffer memory of the board is momentarily full, the service procedure writes the corresponding message to the record queue. Reassignment at the beginning prevents data loss and prevents reordering of the data.

When one stream message is delivered to FDDI board by write service procedure, it is necessary to check whether SMT connection is established. Board status can be checked by reading registers with board status information. The driver 20 and the SMT connection state are possible by accessing the control structure of the driver.

Since the data transmitted between the host and the board cannot be transmitted in the form of a stream message, the data is transmitted using a data structure called a buffer control block (BCB) defined by the network interface driver 20.

Therefore, one transmission frame is contained in one BCB structure and transferred to the buffer memory of the FDDI board through the corresponding VMEbus, and the transmission is completed by sending an interrupt to the FDDI board to inform the board that the data has been transferred. The transmission procedure is repeatedly performed for all stream messages waiting in the recording queue.

When data is transmitted between the network interface driver and the FDDI board, it cannot always be processed immediately by the sender and receiver. VME areas for data transmission and reception must be separated from each other, and thus, arbitrary data flow control functions must be provided.

Accordingly, the RAM device driver 10 and the network interface driver 20 implement a smooth data transfer without loss of information by using a FIFO type circular list called a ring in order to transmit data through the VMEbus.

Figure 8 describes the order in which the ring transfers data between the host driver and the board. The structure of the ring is implemented so that two rings with the same number of entries are paired and can be divided into two types of rings. For data transmission, the ring for data transmission is composed of 256 pairs of data, each consisting of 256 entries to transmit data related to the TCP / IP module, such as a pair for transmitting data from the host to the board, a ring for non_DMA reception, and a ring for DMA reception. It is composed of a processing ring and implements an SMT interface ring having 16 entries to transfer SMT data between a network interface driver and an SMT driver on a board separately from the data transmission ring to transmit and receive information related to SMT.

9 is a block diagram illustrating the address mapping between the virtual address of the network interface driver and the address of the FDDI board according to the present invention. As shown in the drawing, the ring entry is an address of a BCB structure represented as a virtual address of a kernel accessible from the host. The board uses the start address provided by the host to translate these pointers into internal addresses.

After the FDDI board receives one data frame from the network, it performs the FDDI protocol function on the board and generates an FDDI interrupt that executes the FDDI interrupt processing routine implemented in the kernel to deliver the data to the host.

Therefore, since each FDDI board assigns a unique interrupt number at system boot, the network interface driver can know from which board the interrupt is requested.

FIG. 10 is a flowchart illustrating a process of delivering a data received from a communication network to a driver of a host by an FDDI board older device according to the present invention. The frame received by the FDDI board from the communication network through the interrupt routine of the network interface driver 20 is TCP. Describes the processing sequence to pass to the / IP module.

The result of this interrupt routine processing consists of the received data in a stream message, which is allocated to the driver's read queue and transferred to the upper level module by the read service procedure, which is given control by the stream scheduler.

The received data processing method performs the following three processing procedures according to the nature of the data.

First, after the data corresponding to one frame transferred from the host to the board is normally received from the board, the FDDI board generates an interrupt notifying the completion of transmission to the host of the network interface.

In the second case, the board is executed to deliver SMT-related information to the host and notifies the host of SMT events.

When the system boots and requests the SMT connection to the FDDI board through the network interface driver, the board notifies the host through the interrupt of the result of performing the SMT connection. The SMT status information and the double ring of the FDDI network are established when the connection is established normally. Sends an event to the host indicating that data is to be sent to the first ring.

Third, the FDDI board converts all data frames into BCB structures to transfer data arriving through the network to the host, configures and allocates entries to a data receiving ring with a circular list structure, and generates an interrupt to the host to generate network interrupts. Run the routine.

The driver's interrupt routine takes the first entry in the data reception ring, checks for errors, transforms the BCB's data fields into stream messages, and re-reads the DL_UNITDATA_IND primitive to make it visible to the parent module TCP / IP module. In this case, only data fields except the SA field and the DA field, which are physical addresses of the FDDI frame, are configured as stream messages and allocated to the read queue. In this way, all entries in the data receiving ring are transformed into stream messages and placed in the read queue of the network interface driver, and a read service procedure is performed by the stream scheduler.

The role of the read service procedure only serves to deliver stream messages queued to the read queue to the read queue of the upper module.

The FDDI drive device of the present invention has a standard interface in the Unix kernel or between the kernel and other parts by a stream mechanism, thereby increasing mobility between systems and easily transmitting information in the system V version (SVR4.0) of the Unix system. Has the advantage.

Claims (9)

Implemented in the Unix system kernel (SVR 4.0), the RAM device driver transfers data character-by-character between applications and FDDI boards in the system, and interacts in the form of stream message data with TCP / IP modules in the Unix kernel. Fiber distribution data interface (FDDI) board driving apparatus using the stream method in the UNIX system kernel, characterized by consisting of a network interface driver that performs data transmission and reception between. The RAM device driver of claim 1, wherein the RAM device driver comprises a state information access program that downloads firmware onto an FDDI board, retrieves or specifies a state of the board, and uses a stream method in a UNIX system kernel. Fiber Distribution Data Interface (FDDI) Board Driver. The RAM device driver of claim 1, wherein the RAM device driver copies a user area data to a virtual address area of the kernel by using a function to download the data to a board, and transfers the data of the user area to the buffer memory of the FDDI board through the VMEbus. Fiber Distribution Data Interface (FDDI) board driver using stream method in UNIX system kernel. The I / O device of claim 1, wherein the RAM device driver assigns or retrieves a variable value to a portion specifying a register value of the board to start or stop the FDDI board and an SMT driver operating in software on the FDDI board. Fiber distribution data interface (FDDI) board driving apparatus using a stream method in the UNIX system kernel, characterized in that it has a control function. The write foot procedure 51 according to claim 1, wherein the network interface driver receives a message from a TCP / IP module, which is an upper module, and determines a type of the message, and when the message is received by the write foot procedure 51. After setting the driver according to the message and transmitting the driver setting manager 52 to the write foot procedure 51 and the FDDI frame header, the received message is configured as a frame and transmitted to the write foot procedure 51. The frame constructor 51, a write service procedure 54 for controlling a message received from the write foot procedure 51 to be written on the FDDI board, and a message to the FDDI board under the control of the write service procedure 54. A write ring manager 55 for creating a message, and a temporary form for storing a message in a stream form to be read or written through a network interface driver. A stream scheduler 56, a read ring manager 58 for reading messages from the FDDI board, an interrupt handler 57 for recognizing the fact that a message has been delivered from the read ring manager 58, and an FDDI; Drives the Fiber Distribution Data Interface (FDDI) board using the stream method in the UNIX system kernel, characterized by a read service procedure 59 that controls to send messages read from the board to the upper module TCP / IP module. Device. The fiber distribution data of claim 1, wherein the network interface driver transmits data through a buffer control block structure when transmitting data to an FDDI board through a VMEbus. Interface (FDDI) board drive. The network interface driver of claim 1, wherein the M_IOCTL data type performs an access function for control information for the stream interface type, and the message of the M_PROTO data type includes a primitive structure for the interface, each independently according to these primitive structures. By using the stream method in the UNIX system kernel, the stream message is composed of one FDDI frame by an operation of a write foot procedure that performs a function of controlling a stream link or transmitting stream data. Fiber Distribution Data Interface (FDDI) Board Driver. The FDDI driver according to claim 1, wherein when the FDDI board receives data from the network, the network interface driver processes a frame and generates an interrupt to the host according to the corresponding FDDI protocol. The interrupted kernel checks which device is the FDDI driver. A fiber distribution data interface using a stream method in a UNIX system kernel, having a write service procedure for performing an interrupt routine of the controller and configuring the data of the buffer control block structure received by the interrupt according to the stream mechanism. (FDDI) Board drive. The network interface driver of claim 8, wherein the interrupt routine interrupts an interrupt for receiving notification from the FDDI board of a result related to data sent to the FDDI board, and an SMT status information for transmitting status information related to the FDDI communication network to the host. And a stream distribution data interface (FDDI) board driving apparatus using a stream method in a UNIX system kernel, comprising an interrupt for transmitting data arriving from another node of a communication network to a host.