Abstract:
The present invention propose a new mechanism, IP check layer which enables to use TOE cards and legacy NICs simultaneously within same protocol family in a Linux or a UNIX computing environment. The IP check layer is inserted between a BSD socket layer and an INET socket layer. IP check layer maintains a routing information and, information of IP addresses of each network interfaces and each socket&#39;s bind state. Using this information, IP check layer determines how to process a socket call and which layer (TOE layer, host INET layer) will take over the socket call. By means of the above mechanism, the present invention makes existing socket applications to use TOE cards and legacy NICs at the same time without modification or recompiling.

Description:
BACKGROUND OF THE INVENITON  
       [0001]     1. Field of the Invention  
         [0002]     The present invention relates to a device for classifying a protocol family by using an IP in a TOE socket interface, and more particularly, to a protocol family classifying device using IP in a TOE socket interface for supporting both of a TOE card and a NIC in a Linux or a UNIX computing environment.  
         [0003]     2. Description of the Related Art  
         [0004]      FIG. 1  is a diagram illustrating a network software layer architecture in a Linux environment for using a conventional TCP offload engine (TOE).  
         [0005]     As shown in  FIG. 1 , generally, there has been no single socket interface provided for supporting both of a TCP offload engine (TOE) card and conventional network interface cards (NICs) in a UNIX or a Linux computing environment. Therefore, in order to provide a socket interface of TOE, a specific TOE application programming interface (API)  10  must be installed or a TOE protocol family  11  must be additionally implemented in a network module of the UNIX or the Linux.  
         [0006]     However, a device using the API  10  or the TOE protocol family  11  for providing the socket interface of the TOE must be used by modifying application programs and re-compiling the modified application programs.  
         [0007]     Meanwhile, an Ethernet communication technique includes additional functions for reducing and recovering errors generated during communication because the Ethernet communication technique is developed for long distance communication. However, the additional functions may degrade a communication performance in a system level network such as a cluster. Therefore, virtual interface architecture (VIA) for a system area network (SAN) has been introduced as a network protocol. The VIA does not includes additional functions for reducing and recovering errors but it guarantees fast communication.  
         [0008]     However, the VIA does not provide the socket interface.  
         [0009]     Accordingly, there have been various studies in progress for using the socket interface in the system level network protocol and representative one of studies is a socket over VIA (SOVIA) using a socket interface in the VIA.  
         [0010]     However, the SOVIA provides the socket interface on a predetermined protocol.  
       SUMMARY OF THE INVENTION  
       [0011]     Accordingly, the present invention is directed to a protocol family classifying device using an IP in a TOE socket interface for supporting both of a TOE card and a NIC, which substantially obviates one or more problems due to limitations and disadvantages of the related art.  
         [0012]     It is an object of the present invention to provide a protocol family classifying device using an IP in a TOE socket interface for supporting both of a TOE card and a NIC in a network environment such as TCP/IP and UDP by classifying a socket call of TCP/IP layer and a socket call of TOE network layer and transferring classified socket call to corresponding layer by using an IP address.  
         [0013]     Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.  
         [0014]     To achieve these objects and other advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, there is provided a device for classifying a protocol family by using IP in a socket interface supporting a TOE, wherein an IP Check layer is inserted between a BSD socket and an INET socket, the IP Check layer maintains a routing information and an IP information of network interfaces in lower layer and the device classifies and processes socket calls according to IP address of each socket calls.  
         [0015]     It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0016]     The accompanying drawings, which are included to provide a further understanding of the invention, are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the principle of the invention. In the drawings:  
         [0017]      FIG. 1  is a diagram illustrating a network software layer architecture in a Linux environment for using a conventional TCP offload engine (TOE);  
         [0018]      FIG. 2  is a diagram illustrating a TOE socket software layer architecture including an IP CHECK layer in accordance with a preferred embodiment of the present invention;  
         [0019]      FIG. 3  is a flowchart illustrating a procedure for processing BIND call in an IP check layer  20  in accordance with a preferred embodiment of the present invention;  
         [0020]      FIG. 4  is a flowchart showing a procedure for processing a LISTEN call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0021]      FIG. 5  is a flowchart showing a procedure for calling ACCEPT in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0022]      FIG. 6  is a flowchart illustrating a procedure for processing a CONNECT call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0023]      FIG. 7  is a flowchart showing a procedure for processing SENDMSG call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0024]      FIG. 8  is a flowchart showing a procedure for processing RECVMSG in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0025]      FIG. 9  is a flowchart showing a procedure for processing GETNAME in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0026]      FIG. 10  is a flowchart showing a procedure for processing POLL call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0027]      FIG. 11  is a flowchart showing a procedure for processing SHUTDOWN in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0028]      FIG. 12  is a flowchart showing a procedure for processing SETSOCKOPT in the IP CHECK layer in accordance with a preferred embodiment of the present invention;  
         [0029]      FIG. 13  is a flowchart showing a procedure for processing GETSOCKOPT in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0030]      FIG. 14  is a flowchart showing a procedure for processing a RELEASE in the IP CHECK layer in accordance with a preferred embodiment of the present invention;  
         [0031]      FIG. 15  is a flowchart showing a procedure for processing GROUP  1  of IOCTL in the IP CHECK layer in accordance with a preferred embodiment of the present invention;  
         [0032]      FIG. 16  is a flowchart showing a procedure for processing commands in GROUP  2  of IOCTL in the IP CHECK layer  20  in a preferred embodiment of the present invention;  
         [0033]      FIG. 17  is a flowchart showing a procedure for processing commands in GROUP  3  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0034]      FIG. 18  is a flowchart showing a procedure for processing commands in GROUP  4 - 5  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0035]      FIG. 19  is a flowchart showing a procedure for processing commands in GROUP  6  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0036]      FIG. 20  is a flowchart showing a procedure for processing commands in GROUP  7  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention;  
         [0037]      FIG. 21  is a flowchart showing a procedure for processing commands in GROUP  8  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention; and  
         [0038]      FIG. 22  is a flowchart showing a procedure for processing commands in GROUP  9 - 11  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0039]     Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.  
         [0040]      FIG. 2  is a diagram illustrating a TOE socket software layer architecture including an IP CHECK layer in accordance with a preferred embodiment of the present invention.  
         [0041]     An internet protocol (IP) address is allocated to each of network interface cards for classifying a transmission control protocol/internet protocol (TCP/IP) layer  21  and a TCP offload engine (TOE) layer  22  under a socket layer in the present invention.  
         [0042]     As shown in  FIG. 2 , network interface card (NIC) drivers  23  and  24  are connected to the TCP/IP layer  21  as a lower layer and a TCP offload engine (TOE) card driver  25  is connected to a TOE layer  22  as a lower layer.  
         [0043]     Generally, a unique IP address is assigned to each of the network interface cards and parameters of each socket are transferred to a layer including a network interface card having corresponding IP address. For transferring the parameters to corresponding IP address in the present invention, a routing table is maintained in the IP check layer  20  and the routing table includes information of network address of each network interface card and information of routing.  
         [0044]     Meanwhile, the UNIX and the Linux provides various socket commands such as BIND, LISTEN, ACCEPT, SENDMSAG, RECVMSAG, GETNAME, IOCTL, POLL, SHUTDOWN, GETWOCKOPT and SETSOCKOPT.  
         [0045]     The protocol family classifying device of the present invention determines a layer to transfer a call from the IP check layer based on each socket call. Hereinafter, the device of the present invention is explained by referring to FIGS.  3  to  22 .  
         [0046]     1. BIND  
         [0047]      FIG. 3  is a flowchart illustrating a procedure for processing BIND call in an IP check layer  20  in accordance with a preferred embodiment of the present invention.  
         [0048]     The BIND allocates a local IP address and a port number to a local host in a TCP/IP connection. The local host and a remote host are connected in the TCP/IP connection.  
         [0049]     It is possible to allocate the local IP address by using one of an assigned IP address in lower layer or ANY_ADDRESS. The assigned IP address is one of IP addresses assigned to registered network interface cards and the ANY_ADDRESS means IP address will be assigned thereafter.  
         [0050]     As shown in  FIG. 3 , the IP check layer  20  transfers a call to a lower layer including the assigned IP address at step  32  in case of the assigned IP address  30   
         [0051]     In contrary, in case of the ANY_ADDRESS, the BIND call is transferred to both of two layers at step  33 . That is, allocation of IP address is delayed until the IP address is decided to one of the assigned IP address.  
         [0052]     Also, when the port number is specified by a user, the specified port number is checked whether the specified port number is currently used. If the specified port number is not currently used, the specified port number is assigned and if not, an error message is returned to the user. If the user specifies the port number as “0”, one of un-used port numbers is automatically assigned.  
         [0053]     2. LISTEN  
         [0054]      FIG. 4  is a flowchart showing a procedure for processing a LISTEN call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0055]     The LISTEN elucidates to accept a request of connection to a socket where a connection is not established at a TCP server side.  
         [0056]     Generally, the LISTEN is called after the BIND call. However, if the LISTEN is called before the BIND ( 40 ), the bind is established by using the ANY_ADDRESS and the port number is allocated at step  41 . After allocating the port number, the LISTEN is called at step  42 .  
         [0057]     The LISTEN routes the call to a layer having the assigned IP when the local IP address is allocated to the assigned IP ( 43 ) at step  44 . If the local IP address is bind to the ANY_ADDRESS ( 45 ), calls of both layers are called at step  42   
         [0058]     3. ACCEPT  
         [0059]      FIG. 5  is a flowchart showing a procedure for processing ACCEPT call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0060]     The ACCEPT is called from a server side in the TCP connection and establishes a new connection by selecting one of connection requests in an accept queue. Also, the ACCEPT is not provided in a user datagram protocol (UDP) where the connection is not provided. Also, it is possible to call the ACCEPT only when the BIND is established.  
         [0061]     Referring to  FIG. 5 , if BIND is established to ANY_ADDRESS ( 50 ), ACCEPT of all layers are called at step  51 . If the BIND is established to the assigned IP address ( 52 ), the ACCEPT of corresponding layer having the assigned IP address is called at step  53 .  
         [0062]     When the ACCEPT is performed in a BLOCK mode, a kernel may be blocked at a predetermined layer. Therefore, it has to avoid that the calling of ACCEPT is blocked and stopped at a stack for orderly performing the ACCEPT call in multiple layers when simultaneously performing the ACCEPT call in the multiple layers.  
         [0063]     4. CONNECT  
         [0064]      FIG. 6  is a flowchart illustrating a procedure for processing a CONNECT call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0065]     The CONNECT generates an activated socket connection by requesting a connection to a socket at the server side which is in waiting after LISTEN in case of the TCP. In case of the UDP, the CONNECT assigns an address of target place when SEND is called. The CONNECT also determines a stack to perform the CONNECT according to a state of BIND.  
         [0066]     As shown in  FIG.6 , if BIND is not established  60 , the BIND is established to ANY_ADDRESS at step  61  and orderly performs the CONNECT to all stacks  62  where can route to the address of target calling the CONNECT at step  63  until it finds a stack where a connection can be established to the target address ( 64 ).  
         [0067]     In contrary, if the BIND is established to the assigned IP address ( 65 ), it calls the CONNECT of a layer having the assigned IP address at step  66 .  
         [0068]     Also, the first stack among stacks calling CONNECT is selected in case of the UDP because connections are not established in the UDP.  
         [0069]     SENDMSG  
         [0070]      FIG. 7  is a flowchart showing a procedure for processing SENDMSG call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0071]     The SENDMSG is used for sending data to a socket and it can be used both of cases that a connection is established or not established.  
         [0072]     As shown in  FIG.7 , the SENDMSG analyzes a current state of BIND and SENDMSG is transferred at step  71  when BIND is established to the assigned IP address ( 70 ). If the BIND is established to ANY_ADDRESS ( 72 ), a port number is allocated at first and orderly transfers SENDMSG to all layers ( 73 ) at step  74 .  
         [0073]     RECVMSG  
         [0074]      FIG. 8  is a flowchart showing a procedure for processing RECVMSG in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0075]     The RECVMSG is used for receiving data in a socket.  
         [0076]     As shown in  FIG. 8 , if the BIND is established to the assigned IP address ( 80 ), the RECVMSG is transferred to corresponding layer at step  81 .  
         [0077]     In contrary, the BIND is established to the ANY_ADDRESS ( 82 ), a call of RECVMSG is differently processed according to a block mode or a non-block mode. That is, in case of non-block mode, the RECVMSG is orderly requested to all layers at step  83 . In case of block mode, the RECVMSG is requested to all layers by setting a time out not to be blocked at a specific layer. If there is a layer successfully requested, the RECVMSG process is stopped at step  85 .  
         [0078]     7. GETNAME  
         [0079]      FIG. 9  is a flowchart showing a procedure for processing GETNAME in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0080]     The GETNAME returns a source of a socket, or an address of target. The address includes an IP and a port number.  
         [0081]     As shown in  FIG. 9 , if the BIND is established to IP included in TOE layer  22 , the GETNAME transfers a request to the TOE layer at step  92 . If not ( 92 ), the request of GETNAME is transferred to the host INET socket layer  21 .  
         [0082]     8. POLL  
         [0083]      FIG. 10  is a flowchart showing a procedure for processing POLL call in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0084]     The POLL is used for waiting an event occurred in a file descriptor.  
         [0085]     As shown in  FIG. 10 , if the BIND is set to the assigned IP at step  100 , the POLL transfers the call to a layer having the assigned IP address at step  101 . If the BIND is set to ANY_ADDRESS  102 , the POLL is performed for all layers at step  104 .  
         [0086]     9. SHUTDOWN  
         [0087]      FIG. 11  is a flowchart showing a procedure for processing SHUTDOWN in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0088]     The SHUTDOWN terminates one of ends in a bidirectional connection.  
         [0089]     If BIND is established to the assigned address ( 110 ), the SHUTDOWN transfers a call to a layer having the assigned address at step  111 . If the BIND is established to ANY_ADDRESS, the call is transferred to all layers at step  114 .  
         [0090]     10. SETSOCKOPT  
         [0091]      FIG. 12  is a flowchart showing a procedure for processing SETSOCKOPT in the IP CHECK layer in accordance with a preferred embodiment of the present invention.  
         [0092]     The SETSOCKOPT sets options of a socket.  
         [0093]     As shown in  FIG. 12 , if the current socket is bound to the assigned IP at step  120 , the SETSOCKOPT transfers a call to a layer including the assigned IP at step  121 . If the socket is bound to ANY_ADDRESS at step  122 , a call of SETSOCKOPT is transferred to all layers at step  123 .  
         [0094]     11. GETSOCKOPT  
         [0095]      FIG. 13  is a flowchart showing a procedure for processing GETSOCKOPT in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0096]     The GETSOCKOPT reads options of a current socket.  
         [0097]     As shown in  FIG. 13 , if the current socket is bound to the assigned IP at step  130 , the GETSOCKOPT transfers the call to the layer having the assigned IP at step  131 . If the current socket is bound to ANY_ADDRESS ( 132 ), the call of GETSOCKOPT is transferred to the INET socket layer  210  of the host at step  133 . It is because the INET socket layer  21  of the host takes charge of the socket options in both cases of the current socket bound to the ANY_ADDRESS.  
         [0098]     12. RELEASE  
         [0099]      FIG. 14  is a flowchart showing a procedure for processing a RELEASE in the IP CHECK layer in accordance with a preferred embodiment of the present invention.  
         [0100]     The RELEASE closes a socket. Because the RELEASE closes and releases operations and data related to corresponding sockets in all layer, the RELEASE is transferred to all layers.  
         [0101]     13. IOCTL  
         [0102]     IOCTL performs various operations including setting of a network device. Accordingly, the IOCTL performs different operations according to a command provided from a CMD which transfers variables. Therefore, the IOCTL also performs different operations in IP CHECK layer  20  according to each command provided from the CMD.  
         [0103]     Hereinafter, the IOCTL is explained according to a command group which is processed by identical process in the IP CHECK layer.  
         [0104]     GROUP  1 : FIOSETOWN, SIOCSPGRP  
         [0105]      FIG. 15  is a flowchart showing a procedure for processing GROUP  1  of IOCTL in the IP CHECK layer in accordance with a preferred embodiment of the present invention.  
         [0106]     The GROUP  1  of CMD stores a process group ID or a process ID using the socket calling the IOCTL in the socket. A layer having data structure storing the process ID or the process group ID is the INET socket layer. Accordingly, if the socket calling the IOCTL is bound to the assigned IP address at step  150 , a request of IOCTL is transferred to corresponding layer at step  151 . If it is bound to ANY_ADDRESS ( 152 ) or not bound ( 153 ), the request of IOCTL is transferred to all layers at step  154 .  
         [0107]     GROUP  2 : FIOGETOWN, SIOCGPGRP  
         [0108]      FIG. 16  is a flowchart showing a procedure for processing commands in GROUP  2  of IOCTL in the IP CHECK layer  20  in a preferred embodiment of the present invention.  
         [0109]     The commands in GROUP  2  return a process ID or a process group ID stored in a socket to a user.  
         [0110]     As shown in  FIG. 16 , if a corresponding socket is bound to the assigned IP address ( 160 ), a request of IOCTL is transferred to the corresponding layer at step  161 . If it is bound to ANY_ADDRESS ( 162 ), or is not bound yet ( 163 ), it is possible to transfer the request to any layers because the process ID and the process group ID are stored in both layers. In the preferred embodiment of the present invention, the request of IOCTL is transferred to the host INET socket layer at step  164 .  
         [0111]     GROUP  3 : SIOCGSTAMP  
         [0112]      FIG. 17  is a flowchart showing a procedure for processing commands in GROUP  3  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0113]     The commands in GROUP  3  transfers a time stored in a socket used by timeout functions in the socket to a user. If BIND is established to the assigned IP address ( 170 ), it is transferred to the layer having the assigned IP address at step  170 . If the BIND is established to ANY_ADDRESS ( 172 ), or BIND is not established ( 173 ), it transfers to the host INET socket layer at step  174 . The time is recorded in all layers in a case that BIND is not established or established to ANY_ADDRESS. Therefore, it does not a matter to transfer the request to any layers. In the preferred embodiment, it is transferred to the host INET socket layer for convenience.  
         [0114]     GROUP  4 : SIOCADDRT, SIOCDELRT, SIOCRTMSG  
         [0115]      FIG. 18  is a flowchart showing a procedure for processing commands in GROUP  4  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0116]     The commands in GROUP  4  add an entry or delete the entry in a routing table. The routing table is information required to be maintained in all layers. Therefore, all layers call the IOCTL of GROUP  4  without concerning the state of BIND at step  180 .  
         [0117]     GROUP  5 : SIOCDARP, SIOCGARP, SIOCSARP  
         [0118]     The commands in GROUP  5  are related to an address resolution protocol (ARP). Therefore, it is called at all layers at step  180 .  
         [0119]     GROUP  6 : SIOCGIFADDR, SIOCGIFBRDADDR, SIOCGIFNETMASK  
         [0120]      FIG. 19  is a flowchart showing a procedure for processing commands in GROUP  6  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0121]     The commands in GROUP  6  transfers an IP address assigned by each command. The IP address includes an IP address of a network interface, a broadcasting address and a network mask address.  
         [0122]     In the present invention, a routing information and IP addresses of the network interface cards must be managed in the IP CHECK layer  20 . Accordingly, the request is not necessary to transfer to lower layer. The commands in GROUP  6  are processed in the IP CHECK layer  20  at step  190 .  
         [0123]     GROUP  7 : SIOCSIFADDR, SIOCSIFBRDADDR, SIOCSIFNETMASK, SIOCSIFDSTADDR, SIOCSIFPFLAGS  
         [0124]      FIG. 20  is a flowchart showing a procedure for processing commands in GROUP  7  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0125]     The commands in GROUP  7  assign and change each IP address or a flag. The user assigns a name of network interface as IOCTL variables and a layer having corresponding network interface is found in the IP CHECK layer  20  at step  200  and a call is transferred to corresponding layer.  
         [0126]     GROUP  8 : SIOCGIFBR, SIOCSIFBR, SIOCGIFVLAN, SIOCSIFVLAN  
         [0127]      FIG. 21  is a flowchart showing a procedure for processing commands in GROUP  8  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0128]     The commands in GROUP  8  are calls for predetermined kernel module and they are processed in the INET socket layer at step  210 .  
         [0129]     GROUP  9 : SIOCGIFDIVERT, SIOCSIFDIVERT  
         [0130]      FIG. 22  is a flowchart showing a procedure for processing commands in GROUP  9  of IOCTL in the IP CHECK layer  20  in accordance with a preferred embodiment of the present invention.  
         [0131]     The commands in GROUP  9  are commands related to DIVERT. When the commands in GROUP  9  are called, a name of network interface is included in data transferred by a user where the network interface is a target network interface where the commands are performed. In the IP CHECK layer  20 , it determines a layer where the IOCTL call is transferred to by using the name of network interface included in the data at step  220 .  
         [0132]     GROUP  10 : SIOCADDDLCI, SIOCDELDLCI  
         [0133]     The commands in GROUP  10  are commands for FRAME RELAY protocol. When calling the commands in GROUP  10 , data transferred by a user also includes a name of network interface where the commands are performed. In the IP CHECK layer  20 , it determines a layer where the IOCTL call is transferred to by using the name of network interface included in the data at step  220 .  
         [0134]     GROUP  11 : DEFAULT  
         [0135]     The commands in GROUP  11  include commands not included in the GROUPs  1  to  10 . The commands in GROUP  11  are commands related to sub commands related to network device. When the DEFAULT is called, data also includes a name assigned for target network interface. In the IP CHECK layer  20 , it determines a layer where the IOCTL call is transferred to by using the name of network interface included in the data at step  220 .  
         [0136]     The above mentioned present invention can be implemented as a set of computer executable instructions can be stored in a computer readable recording medium including a read only memory (ROM), a random access memory (RAM), a compact disk (CD)-ROM, a digital video disk(DVD)-ROM, a magnetic tape, a floppy disk and an optical disk. Also, the computer readable recording medium can be distributed to computer systems connected to a network and computer readable code can be stored and performed according to a distribution method.  
         [0137]     As mentioned above, the protocol family classifying device using IP in accordance with the present invention provides a socket interface for using the TOE network card without modifying application programs of the conventional socket interface. Also, the present invention provides the socket interface that supports both of the TOE card and the NIC in same protocol family.  
         [0138]     It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.