US20090046600A1 - Portable networking interface method and apparatus for distributed switching system - Google Patents
Portable networking interface method and apparatus for distributed switching system Download PDFInfo
- Publication number
- US20090046600A1 US20090046600A1 US12/263,687 US26368708A US2009046600A1 US 20090046600 A1 US20090046600 A1 US 20090046600A1 US 26368708 A US26368708 A US 26368708A US 2009046600 A1 US2009046600 A1 US 2009046600A1
- Authority
- US
- United States
- Prior art keywords
- fddl
- switch
- protocol
- device driver
- communicating
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/545—Interprogram communication where tasks reside in different layers, e.g. user- and kernel-space
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/45—Arrangements for providing or supporting expansion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5638—Services, e.g. multimedia, GOS, QOS
- H04L2012/5665—Interaction of ATM with other protocols
- H04L2012/5669—Multiprotocol over ATM [MPOA]
Definitions
- the present invention relates in general to a switching system for use in a network. More particularly, the invention relates to a portable interface method and system for accessing a switch device driver from the various network services applications supported by a switch.
- Each network operates on the basis of one or more switches which route digital data from an originating device to a destination device.
- communication protocols have been developed in order to standardize and streamline communications between devices and promote connectivity.
- a switch can represent a large capital investment in a network system.
- the frequency in which new protocols are developed makes it impractical to upgrade switches with every protocol introduced to the market. Accordingly, what is needed is a system and device for improving interface portability within the switch so that switches can be quickly and easily upgraded and new network interface protocols can be written and supported on multiple switch fabrics.
- the invention solves the problem of portability by defining two primary interfaces within the switch.
- the first interface is called the Forwarding Database Distribution Library (FDDL) Application Program Interface (API).
- FDDL Forwarding Database Distribution Library
- API Application Program Interface
- the primary purpose of this interface is to allow each protocol application to distribute its database and functionality to intelligent port controllers within the switch. Such distribution facilitates hardware forwarding at the controller.
- Each protocol application may define a specific set of FDDL messages that are exchanged between the protocol application and the switch fabric, which passes the messages to software running at each port controller.
- the second interface defined by the invention is called the Switch Services API.
- This interface is primarily a generic way for controlling data message flow between the ports interfaces and the switch device driver.
- a set of specific messages is defined to allow uniform exchange of information about the hardware status of the port as well as an interface for sending and receiving data frames.
- FIG. 1 is a system block diagram of a network switch, including workstations connected to the network switch;
- FIG. 2 is a system block diagram of a data processing system which may be used as a workstation within the present invention
- FIG. 3 is a block diagram describing the FDDL defined by the present invention and its relationship with the switch device driver and protocol drivers;
- FIG. 4 is a software system block diagram of a portion of a network switch embodying the present invention which describes the relationship between the FDDL, the other services provided by the switch, and the in relation to the switch device driver;
- FIG. 5 is a system block diagram of the software architecture within a network switch embodying the present invention.
- FIG. 6 is a flow chart according to ANSI/ISO Standard 5807-1985 depicting the operation of the basic primitives defined by the Switch Services API of the instant invention.
- FIG. 7 is a flow chart according to ANSI/ISO Standard 5807-1985 demonstrating the operation of the FDDL API as defined by the instant invention.
- a network switch 100 is comprised of one or more intelligent port controllers 110 , a switch fabric 112 , and a central processing unit (CPU) 114 .
- the switch 100 is connected to one or more backbones 104 , which in turn are connected to one or more workstations 102 .
- Each intelligent port controller 110 may be connected to one or more backbones 104 comprising a local area network (LAN) 106 .
- the entire system may be referred to as a network 108 .
- the switch fabric 112 is comprised of one or more processors that manage a shared pool of packet/cell memory.
- the switch fabric 112 controls the sophisticated queuing and scheduling functions of the switch 100 .
- the intelligent port controller 110 provides connectivity between the switch fabric 112 and the physical layer devices, such as the backbones 104 .
- the intelligent port controller 110 may be implemented with one or more bitstream processors.
- a typical workstation 102 is depicted with reference to FIG. 2 , which illustrates the typical hardware configuration of workstation 213 in accordance with the subject invention.
- the workstation 213 includes a central processing unit (CPU) 210 , such as a conventional microprocessor and a number of other units interconnected via a system bus 212 .
- the workstation 213 may include a random access memory (RAM) 214 , a read-only memory (ROM) 216 , and an I/O adapter 218 for connecting peripheral devices, such as disk units 220 and tape drives 240 to the bus 212 .
- RAM random access memory
- ROM read-only memory
- I/O adapter 218 for connecting peripheral devices, such as disk units 220 and tape drives 240 to the bus 212 .
- the workstation 213 also include a user interface adapter 222 for connecting a keyboard 224 , a mouse 226 and/or other user interface devices, such as a touch screen device (not shown) to the bus 212 , a communication adapter 234 for connecting the workstation 213 to a network 242 (such as the one depicted on FIG. 1 at 108 ), and a display adapter 236 for connecting the bus 212 to a display device 238 .
- the CPU 210 may include other circuitry not shown, which may include circuitry found within a microprocessor, e.g., execution unit, bus interface unit, arithmetic logic unit (ALU), etc.
- the CPU 210 may also reside on one integrated circuit (IC).
- the FDDL is defined with reference to FIG. 3 .
- the FDDL is a library which defines a set of API's designed to enable protocol forwarding functions to be distributed in a manner that is simple, efficient, and deportable.
- the FDDL 310 is comprised of one or more towers 322 , 324 , 326 , 328 . As depicted, a tower may be provided for remote monitoring (RMON) in an RMON FDDL tower 322 .
- Multi Protocol Over ATM (MPOA) services may be provided through an MPOA client FDDL tower 324 .
- Bridging services may connect through a Bridge FDDL tower 326 .
- IP Internet Protocol
- Autolearn connectivity may be provided through an Autolearn FDDL tower 328 .
- Each of the FDDL towers 322 , 324 , 326 , 328 is connected through the FDDL API 332 to its respective protocol services of the RMON application 314 , the MPOA application 316 , the Bridge 318 , and the IP Autolearn application 320 , as provided within the switch.
- the FDDL 310 functions to receive commands from the various protocol components 314 , 316 , 318 , 320 into the corresponding FDDL towers 322 , 324 , 326 , 328 .
- a command is received into a tower 322 , 324 , 326 , 328 , it is passed to the base FDDL subsystem 330 for translation and passage directly to the switch device driver 312 through the Switch Services API 334 .
- the operation of the Switch Services API is demonstrated with reference to FIG. 4 .
- the switch device driver 420 resides immediately below FDDL in the CPU protocol stack. As shown, there may be several users of the Switch Service API 410 which communicate with the switch device driver 420 . In addition to the FDDL towers 418 , other users may include an Ethernet Device Driver Shim 416 and an Asynchronous Transfer Mode (ATM) Device Driver Shim 414 .
- the Device Driver Shims 414 , 416 are interface translation agents which complete the high-level of architecture of the switch.
- the shims translate between the existing device driver interfaces and the Switch Services API 410 of the instant invention. In this way, translation through the shims 414 , 416 allows preservation of the existing device driver interfaces from the ATM and Ethernet protocols and avoids modification of those handlers for use with the switch services API 410 .
- the bridging protocol application 412 may also communicate directly with the switch device driver 420 through the Switch Services API 410 .
- FIG. 5 is a block diagram depicting the basic software architecture of a network switch embodying the instant invention. While the software depicted is depicted as running on a Power PC processor 510 and on the OS Open real time operating system 512 , those skilled in the art will appreciate that the instant invention can be practiced with a number of processors running a number of different operating systems. However, since the Power PC platform is the preferred technology for products employing many of the networking technology described, it present many advantages with regard to the architectural goals of the instant invention.
- the Power PC box 518 is connected to the switch fabric 514 through the Switch Device Driver 516 .
- the switch fabric 514 is connected to one or more port controllers 520 .
- the Switch Device Driver 516 supports a Switch Services API 522 through which it can send and receive messages to the FDDL 524 , as well as the ATM Device Driver Shim 526 and the Ethernet Device Driver Shim 528 .
- the ATM Device Driver Shim 526 and the Ethernet Device Driver Shim 528 connect to their respective net handlers 530 , 532 through device driver interfaces 534 , 536 .
- the MPOA client 538 may communicate to the switch device driver either through the ATM API 540 or through the FDDL API 542 as defined by the FDDL 524 .
- the bridge services 544 including the Virtual LAN (VLAN) and IP Autolearn services may be provided through the Ethernet Net Handler 532 , through the FDDL API 542 to the FDDL 524 , or LAN Emulation Client (LEC) 546 may be provided to communicate through the ATM API 540 to the ATM Net Handler 530 .
- VLAN Virtual LAN
- LEC LAN Emulation Client
- the operating system 512 features such as Simple Network Management Protocol (SNMP) and RMON 548 , other box services 550 , and IP hosting services 552 , such as Telnet, Ping, and other may be provided.
- SNMP Simple Network Management Protocol
- RMON 548 other box services 550
- IP hosting services 552 such as Telnet, Ping, and other may be provided.
- the operation of the Switch Services API 522 as provided by the switch device driver 516 is shown with reference to FIG. 6 .
- Execution begins 610 without precondition.
- the API is initiated with a switch_registration( ) call 612 to register an interface user of the Switch Services API.
- the registration call includes parameters of a code point identifying the interface application that is registering with the API and pointers to up-call functions which may be called when messages or data frames associated with the application are received by the switch device driver to be passed through the API.
- the API is active 614 . While the API is active, calls may be made to at least any one of four primitives, including switch_send_MSG( ) 616 , switch_send_data ( ) 618 , switch_get_buffer ( ) 620 , and switch_free_buffer ( ) 622 .
- the switch_send_MSG( ) primitive 616 is called to transmit a message to one or more registered interfaces. Messages may be sent to one interface, a group of interfaces, or broadcast to all interfaces. A message may be generally formatted using the Type-Length-Value (TLV) convention.
- TLV Type-Length-Value
- the switch_send_data( ) primitive 618 is called to transmit a data frame out of one or more interfaces.
- the set of destination interfaces may be specified with a bit mask or by other means well-appreciated within the art.
- the switch_get buffer( ) primitive 620 is called to allocate frame buffers. Conversely, the switch_free_buffer( ) primitive 622 is called to deallocate frame buffers.
- Calls to the primitives may continue as long as the API is active 624 .
- an interface application wishes to disable the API, it does so by calling switch_deregistration( ) 626 , which deregisters the application as a user of the switch services API. Execution of the Switch Services API then ceases 628 .
- the operation of the base FDDL subsystem is demonstrated with reference to FIG. 7 .
- Execution begins 710 without pre-condition.
- the FDDL_registration( ) primitive 712 is called to register a client application as a user of the FDDL API.
- a call to the FDDL_registration( ) primitive 712 specifies a code point identifying the data base of the calling application (e.g. bridging, MPOA, etc.) and provides a pointer to a message-reception call-back function that can be invoked when messages related to the specified client are received by the API.
- the FDDL is active 714 , beginning a looping process of calls.
- the FDDL_send( ) primitive 716 may be called to initiate transmission of a message from the CPU to one or more adapters.
- the message may be transmitted to a single adapter or broadcast to all adapters.
- the FDDL_registration status( )primitive 718 may be called query whether a particular database is currently registered with the FDDL API.
- the primitive_deregistration( ) 722 may be called to deregister a client application as a user of the FDDL API. Following the call to the FDDL_deregistration( ) 722 , execution of the FDDL subsystem ceases 724 .
- each of the FDDL towers as shown on FIG. 3 including the RMON tower 322 , the MPOA tower 324 , the Bridge tower 326 , and the IP Autolearn tower 328 may each be optimized with primitives adapted to their respective applications 314 , 316 , 318 , 320 .
- primitives need not be written for each tower and that additional towers may be added for client applications to be added in the future.
- the base FDDL subsystem 330 and its primitives may remain unchanged in order to provide a universal interface to the switch device driver 312 .
- the FDDL towers 322 , 324 , 326 , 328 may each have its own registration processes that allow instances of its specific protocol client applications to register. Additionally, those skilled in the art will appreciate that the FDDL tower calls may be providing for other networking features well-known in the art, such as providing reliable delivery of messages, acknowledgment and non-acknowledgment schemes, Cyclic Redundancy Code (CRC) code checking, and the like.
- CRC Cyclic Redundancy Code
- Switch Services API need not provide for such flexibility.
- the Switch Device Drivers 312 are hardware dependent relying on the switch fabric ( FIG. 5 , 514 ) for their definition. As hardware will not be replaced or upgraded as easily or frequently as the client applications, the Switch Services API need not provide a towering structure.
Abstract
An apparatus and method to provide a portable networking interface for distributed switching systems. Two Application Program Interfaces (APIs) are defined for communication to a Forwarding Database Distribution Library (FDDL). The FDDL sits between network client applications and the switch device driver in order to provide a uniform interface to the switch device driver. Towers may be added to the FDDL to provide additional functionality specific to certain client applications.
Description
- The present invention relates in general to a switching system for use in a network. More particularly, the invention relates to a portable interface method and system for accessing a switch device driver from the various network services applications supported by a switch.
- The proliferation of personal computers, digital telephones, telephony and telecommunications technology has resulted in the development of complex switches in order to efficiently communicate digital data between a number of different devices. These communication systems are generally referred to as networks. Each network operates on the basis of one or more switches which route digital data from an originating device to a destination device. To this end, communication protocols have been developed in order to standardize and streamline communications between devices and promote connectivity.
- As advances are made in telecommunications and connectivity technology, additional protocols are rapidly being developed in order to improve the efficiency and interconnectivity of networking systems. As these advances occur, modifications are required to the switches in order to allow the switches to appropriately deal with the new protocols and take advantage of the new efficiencies that they offer.
- Unfortunately, a switch can represent a large capital investment in a network system. The frequency in which new protocols are developed makes it impractical to upgrade switches with every protocol introduced to the market. Accordingly, what is needed is a system and device for improving interface portability within the switch so that switches can be quickly and easily upgraded and new network interface protocols can be written and supported on multiple switch fabrics.
- The invention solves the problem of portability by defining two primary interfaces within the switch. The first interface is called the Forwarding Database Distribution Library (FDDL) Application Program Interface (API). The primary purpose of this interface is to allow each protocol application to distribute its database and functionality to intelligent port controllers within the switch. Such distribution facilitates hardware forwarding at the controller. Each protocol application may define a specific set of FDDL messages that are exchanged between the protocol application and the switch fabric, which passes the messages to software running at each port controller.
- The second interface defined by the invention is called the Switch Services API. This interface is primarily a generic way for controlling data message flow between the ports interfaces and the switch device driver. A set of specific messages is defined to allow uniform exchange of information about the hardware status of the port as well as an interface for sending and receiving data frames.
- The forgoing broadly outlines the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereafter, which form the basis of the claims of the invention.
- For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanied drawings, in which:
-
FIG. 1 is a system block diagram of a network switch, including workstations connected to the network switch; -
FIG. 2 is a system block diagram of a data processing system which may be used as a workstation within the present invention; -
FIG. 3 is a block diagram describing the FDDL defined by the present invention and its relationship with the switch device driver and protocol drivers; -
FIG. 4 is a software system block diagram of a portion of a network switch embodying the present invention which describes the relationship between the FDDL, the other services provided by the switch, and the in relation to the switch device driver; -
FIG. 5 is a system block diagram of the software architecture within a network switch embodying the present invention; -
FIG. 6 is a flow chart according to ANSI/ISO Standard 5807-1985 depicting the operation of the basic primitives defined by the Switch Services API of the instant invention; and -
FIG. 7 is a flow chart according to ANSI/ISO Standard 5807-1985 demonstrating the operation of the FDDL API as defined by the instant invention. - In the following description, numerous specific details are set forth such as languages, operating systems, microprocessors, workstations, bus systems, networking systems, input/output (I/O) systems, etc., to provide a thorough understanding of the invention. However, it will be obvious to those skilled in the art that the present invention may be practiced without such specific details. In other instances, well-known circuits, computer equipment, network protocols, programming configurations, or wiring systems have been shown in blocked diagram form in order to not obscure the present invention in unnecessary detail. For the most part, details concerning timing considerations, specific equipment used, specific programming languages and protocols used, specific networking systems used, and the like have been omitted in as much as these details are not necessary to obtain a complete understanding of the present invention and are well within the skills of persons of ordinary skill in the art.
- The switch to which the present invention relates is shown with reference to
FIG. 1 . Anetwork switch 100 is comprised of one or moreintelligent port controllers 110, aswitch fabric 112, and a central processing unit (CPU) 114. Theswitch 100 is connected to one ormore backbones 104, which in turn are connected to one ormore workstations 102. Eachintelligent port controller 110 may be connected to one ormore backbones 104 comprising a local area network (LAN) 106. The entire system may be referred to as anetwork 108. - The
switch fabric 112 is comprised of one or more processors that manage a shared pool of packet/cell memory. Theswitch fabric 112 controls the sophisticated queuing and scheduling functions of theswitch 100. - The
intelligent port controller 110 provides connectivity between theswitch fabric 112 and the physical layer devices, such as thebackbones 104. Theintelligent port controller 110 may be implemented with one or more bitstream processors. - A
typical workstation 102 is depicted with reference toFIG. 2 , which illustrates the typical hardware configuration ofworkstation 213 in accordance with the subject invention. Theworkstation 213 includes a central processing unit (CPU) 210, such as a conventional microprocessor and a number of other units interconnected via asystem bus 212. Theworkstation 213 may include a random access memory (RAM) 214, a read-only memory (ROM) 216, and an I/O adapter 218 for connecting peripheral devices, such asdisk units 220 andtape drives 240 to thebus 212. Theworkstation 213 also include auser interface adapter 222 for connecting akeyboard 224, amouse 226 and/or other user interface devices, such as a touch screen device (not shown) to thebus 212, acommunication adapter 234 for connecting theworkstation 213 to a network 242 (such as the one depicted onFIG. 1 at 108), and adisplay adapter 236 for connecting thebus 212 to adisplay device 238. TheCPU 210 may include other circuitry not shown, which may include circuitry found within a microprocessor, e.g., execution unit, bus interface unit, arithmetic logic unit (ALU), etc. TheCPU 210 may also reside on one integrated circuit (IC). - The FDDL is defined with reference to
FIG. 3 . The FDDL is a library which defines a set of API's designed to enable protocol forwarding functions to be distributed in a manner that is simple, efficient, and deportable. The FDDL 310 is comprised of one ormore towers tower 322. Multi Protocol Over ATM (MPOA) services may be provided through an MPOA client FDDLtower 324. Bridging services may connect through a Bridge FDDL tower 326. Internet Protocol (IP) Autolearn connectivity may be provided through an Autolearn FDDL tower 328. - Each of the FDDL
towers API 332 to its respective protocol services of theRMON application 314, theMPOA application 316, the Bridge 318, and the IP Autolearnapplication 320, as provided within the switch. - The FDDL 310 functions to receive commands from the
various protocol components towers tower base FDDL subsystem 330 for translation and passage directly to theswitch device driver 312 through theSwitch Services API 334. - The operation of the Switch Services API is demonstrated with reference to
FIG. 4 . Theswitch device driver 420 resides immediately below FDDL in the CPU protocol stack. As shown, there may be several users of theSwitch Service API 410 which communicate with theswitch device driver 420. In addition to the FDDL towers 418, other users may include an EthernetDevice Driver Shim 416 and an Asynchronous Transfer Mode (ATM)Device Driver Shim 414. The Device Driver Shims 414, 416 are interface translation agents which complete the high-level of architecture of the switch. The shims translate between the existing device driver interfaces and theSwitch Services API 410 of the instant invention. In this way, translation through theshims switch services API 410. - The
bridging protocol application 412 may also communicate directly with theswitch device driver 420 through theSwitch Services API 410. - The architecture into which the FDDL and APIs of the instant invention fit is demonstrated with reference to
FIG. 5 , which is a block diagram depicting the basic software architecture of a network switch embodying the instant invention. While the software depicted is depicted as running on aPower PC processor 510 and on the OS Open realtime operating system 512, those skilled in the art will appreciate that the instant invention can be practiced with a number of processors running a number of different operating systems. However, since the Power PC platform is the preferred technology for products employing many of the networking technology described, it present many advantages with regard to the architectural goals of the instant invention. - The
Power PC box 518 is connected to theswitch fabric 514 through theSwitch Device Driver 516. In turn, theswitch fabric 514 is connected to one ormore port controllers 520. TheSwitch Device Driver 516 supports aSwitch Services API 522 through which it can send and receive messages to theFDDL 524, as well as the ATMDevice Driver Shim 526 and the EthernetDevice Driver Shim 528. The ATMDevice Driver Shim 526 and the EthernetDevice Driver Shim 528 connect to their respectivenet handlers - The
MPOA client 538 may communicate to the switch device driver either through theATM API 540 or through theFDDL API 542 as defined by theFDDL 524. Thebridge services 544, including the Virtual LAN (VLAN) and IP Autolearn services may be provided through theEthernet Net Handler 532, through theFDDL API 542 to theFDDL 524, or LAN Emulation Client (LEC) 546 may be provided to communicate through theATM API 540 to theATM Net Handler 530. - Through the structure defined, the
operating system 512 features such as Simple Network Management Protocol (SNMP) andRMON 548,other box services 550, andIP hosting services 552, such as Telnet, Ping, and other may be provided. - The operation of the
Switch Services API 522 as provided by theswitch device driver 516 is shown with reference toFIG. 6 . Execution begins 610 without precondition. The API is initiated with a switch_registration( ) call 612 to register an interface user of the Switch Services API. The registration call includes parameters of a code point identifying the interface application that is registering with the API and pointers to up-call functions which may be called when messages or data frames associated with the application are received by the switch device driver to be passed through the API. - Once the switch _registration( ) called 612 is made, the API is active 614. While the API is active, calls may be made to at least any one of four primitives, including switch_send_MSG( ) 616, switch_send_data ( ) 618, switch_get_buffer ( ) 620, and switch_free_buffer ( ) 622.
- The switch_send_MSG( ) primitive 616 is called to transmit a message to one or more registered interfaces. Messages may be sent to one interface, a group of interfaces, or broadcast to all interfaces. A message may be generally formatted using the Type-Length-Value (TLV) convention.
- The switch_send_data( ) primitive 618 is called to transmit a data frame out of one or more interfaces. When a frame is to be transmitted to more than one interface, the set of destination interfaces may be specified with a bit mask or by other means well-appreciated within the art.
- The switch_get buffer( ) primitive 620 is called to allocate frame buffers. Conversely, the switch_free_buffer( ) primitive 622 is called to deallocate frame buffers.
- Calls to the primitives may continue as long as the API is active 624. When an interface application wishes to disable the API, it does so by calling switch_deregistration( ) 626, which deregisters the application as a user of the switch services API. Execution of the Switch Services API then ceases 628.
- The operation of the base FDDL subsystem is demonstrated with reference to
FIG. 7 . Execution begins 710 without pre-condition. The FDDL_registration( ) primitive 712 is called to register a client application as a user of the FDDL API. A call to the FDDL_registration( ) primitive 712 specifies a code point identifying the data base of the calling application (e.g. bridging, MPOA, etc.) and provides a pointer to a message-reception call-back function that can be invoked when messages related to the specified client are received by the API. - After the primitive FDDL_registration( ) is called, the FDDL is active 714, beginning a looping process of calls.
- Within the loop, the FDDL_send( ) primitive 716 may be called to initiate transmission of a message from the CPU to one or more adapters. The message may be transmitted to a single adapter or broadcast to all adapters. The FDDL_registration status( )primitive 718 may be called query whether a particular database is currently registered with the FDDL API.
- When it is no longer desired for the FDDL to be active 720, the primitive_deregistration( ) 722 may be called to deregister a client application as a user of the FDDL API. Following the call to the FDDL_deregistration( ) 722, execution of the FDDL subsystem ceases 724.
- It will be well appreciated by those skilled in the art that each of the FDDL towers as shown on
FIG. 3 , including theRMON tower 322, theMPOA tower 324, theBridge tower 326, and theIP Autolearn tower 328 may each be optimized with primitives adapted to theirrespective applications base FDDL subsystem 330 and its primitives may remain unchanged in order to provide a universal interface to theswitch device driver 312. - The FDDL towers 322, 324, 326, 328 may each have its own registration processes that allow instances of its specific protocol client applications to register. Additionally, those skilled in the art will appreciate that the FDDL tower calls may be providing for other networking features well-known in the art, such as providing reliable delivery of messages, acknowledgment and non-acknowledgment schemes, Cyclic Redundancy Code (CRC) code checking, and the like.
- Those skilled in the art will also appreciate that the Switch Services API need not provide for such flexibility. The
Switch Device Drivers 312 are hardware dependent relying on the switch fabric (FIG. 5 , 514) for their definition. As hardware will not be replaced or upgraded as easily or frequently as the client applications, the Switch Services API need not provide a towering structure. - As to the manner of operation and use of the instant invention, the same is made apparent from the foregoing discussion. With respect to the above description, it is to be realized that although embodiments of specific material, representations, primitives, languages, and network configurations are disclosed, those enabling embodiments are illustrative and the optimum relationship for the parts of the invention is to include variations in composition, form, function, and manner of operation, which are deemed readily apparent to one skilled in the art in view of this disclosure. All relevant relationships to those illustrated in the drawings in this specification are intended to be encompassed by the present invention.
- Therefore, the foregoing is considered as illustrative of the principles of the invention, and since numerous modifications will occur to those skilled to those in the art, it is not desired to limit the invention to exact construction and operation shown or described, and a user my resort to all suitable modifications and equivalence, falling within the scope of the invention.
Claims (4)
1-21. (canceled)
22. A computer-readable medium having stored thereon computer-executable instructions for performing the steps comprising:
receiving information at a port controller in a first protocol from a first node machine;
communicating the information from the port controller in the first protocol to a switch fabric;
communicating the information from the switch fabric to a switch device driver within an operating system;
communicating the information from the switch device driver to a Forwarding Database Distribution Library (FDDL); and
communicating the information from the FDDL to a first protocol client;
wherein the FDDL allows each protocol application to distribute its database and functionality to port controllers within the switch fabric, wherein the distribution facilitates hardware forwarding at the port controllers;
wherein said each protocol application defines a specific set of FDDL messages that are exchanged between the protocol application and the switch fabric, wherein the messages are passed to a software running at each of the port controllers.
23. The computer-readable medium of claim 22 having further stored thereon computer-executable instructions for performing the steps comprising:
receiving additional information at a port controller in a second protocol from the first node machine;
communicating the additional information from the port controller in the second protocol to the switch fabric;
communicating the additional information from the switch fabric to the switch device driver within the operating system;
communicating the additional information from the switch device driver to the Forwarding Database Distribution Library (FDDL); and
communicating the additional information from the FDDL to a second protocol client.
24-34. (canceled)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/263,687 US20090046600A1 (en) | 2000-02-25 | 2008-11-03 | Portable networking interface method and apparatus for distributed switching system |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/513,518 US7346075B1 (en) | 2000-02-25 | 2000-02-25 | Portable networking interface method and apparatus for distributed switching system |
US11/752,476 US7480311B2 (en) | 2000-02-25 | 2007-05-23 | Portable networking interface method for distributed switching system |
US12/263,687 US20090046600A1 (en) | 2000-02-25 | 2008-11-03 | Portable networking interface method and apparatus for distributed switching system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/752,476 Continuation US7480311B2 (en) | 2000-02-25 | 2007-05-23 | Portable networking interface method for distributed switching system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090046600A1 true US20090046600A1 (en) | 2009-02-19 |
Family
ID=38606367
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/513,518 Expired - Lifetime US7346075B1 (en) | 2000-02-25 | 2000-02-25 | Portable networking interface method and apparatus for distributed switching system |
US11/752,476 Expired - Lifetime US7480311B2 (en) | 2000-02-25 | 2007-05-23 | Portable networking interface method for distributed switching system |
US11/844,106 Expired - Lifetime US7711001B2 (en) | 2000-02-25 | 2007-08-23 | Portable networking interface method and apparatus for distributed switching system |
US12/263,687 Abandoned US20090046600A1 (en) | 2000-02-25 | 2008-11-03 | Portable networking interface method and apparatus for distributed switching system |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/513,518 Expired - Lifetime US7346075B1 (en) | 2000-02-25 | 2000-02-25 | Portable networking interface method and apparatus for distributed switching system |
US11/752,476 Expired - Lifetime US7480311B2 (en) | 2000-02-25 | 2007-05-23 | Portable networking interface method for distributed switching system |
US11/844,106 Expired - Lifetime US7711001B2 (en) | 2000-02-25 | 2007-08-23 | Portable networking interface method and apparatus for distributed switching system |
Country Status (1)
Country | Link |
---|---|
US (4) | US7346075B1 (en) |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7346075B1 (en) * | 2000-02-25 | 2008-03-18 | International Business Machines Corporation | Portable networking interface method and apparatus for distributed switching system |
US7664110B1 (en) | 2004-02-07 | 2010-02-16 | Habanero Holdings, Inc. | Input/output controller for coupling the processor-memory complex to the fabric in fabric-backplane interprise servers |
US7757033B1 (en) | 2004-02-13 | 2010-07-13 | Habanero Holdings, Inc. | Data exchanges among SMP physical partitions and I/O interfaces enterprise servers |
US7561571B1 (en) * | 2004-02-13 | 2009-07-14 | Habanero Holdings, Inc. | Fabric address and sub-address resolution in fabric-backplane enterprise servers |
US7860961B1 (en) | 2004-02-13 | 2010-12-28 | Habanero Holdings, Inc. | Real time notice of new resources for provisioning and management of fabric-backplane enterprise servers |
US7860097B1 (en) | 2004-02-13 | 2010-12-28 | Habanero Holdings, Inc. | Fabric-backplane enterprise servers with VNICs and VLANs |
US7685281B1 (en) | 2004-02-13 | 2010-03-23 | Habanero Holdings, Inc. | Programmatic instantiation, provisioning and management of fabric-backplane enterprise servers |
US7953903B1 (en) | 2004-02-13 | 2011-05-31 | Habanero Holdings, Inc. | Real time detection of changed resources for provisioning and management of fabric-backplane enterprise servers |
US7873693B1 (en) * | 2004-02-13 | 2011-01-18 | Habanero Holdings, Inc. | Multi-chassis fabric-backplane enterprise servers |
US8868790B2 (en) | 2004-02-13 | 2014-10-21 | Oracle International Corporation | Processor-memory module performance acceleration in fabric-backplane enterprise servers |
US7843907B1 (en) | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway target for fabric-backplane enterprise servers |
US7633955B1 (en) | 2004-02-13 | 2009-12-15 | Habanero Holdings, Inc. | SCSI transport for fabric-backplane enterprise servers |
US7843906B1 (en) | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway initiator for fabric-backplane enterprise servers |
US7990994B1 (en) | 2004-02-13 | 2011-08-02 | Habanero Holdings, Inc. | Storage gateway provisioning and configuring |
US8145785B1 (en) | 2004-02-13 | 2012-03-27 | Habanero Holdings, Inc. | Unused resource recognition in real time for provisioning and management of fabric-backplane enterprise servers |
US8713295B2 (en) | 2004-07-12 | 2014-04-29 | Oracle International Corporation | Fabric-backplane enterprise servers with pluggable I/O sub-system |
US7784065B2 (en) * | 2005-02-07 | 2010-08-24 | Microsoft Corporation | Interface for consistent program interaction with auxiliary computing devices |
US8046519B2 (en) * | 2008-10-20 | 2011-10-25 | Daniel Measurement And Control, Inc. | Coupling a specialty system, such as a metering system, to multiple control systems |
US11080274B2 (en) | 2017-01-17 | 2021-08-03 | Futurewei Technologies, Inc. | Best-efforts database functions |
US10805241B2 (en) * | 2017-01-17 | 2020-10-13 | Futurewei Technologies, Inc. | Database functions-defined network switch and database system |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5732338A (en) * | 1987-07-27 | 1998-03-24 | Prs Corporation | Broadcast receiver capable of autonomous format-scanning, program identification and searching |
US5970069A (en) * | 1997-04-21 | 1999-10-19 | Lsi Logic Corporation | Single chip remote access processor |
US6031843A (en) * | 1996-11-21 | 2000-02-29 | Alcatel Data Networks Inc. | Digital communications switching fabric |
US6032193A (en) * | 1997-03-20 | 2000-02-29 | Niobrara Research And Development Corporation | Computer system having virtual circuit address altered by local computer to switch to different physical data link to increase data transmission bandwidth |
US6076092A (en) * | 1997-08-19 | 2000-06-13 | Sun Microsystems, Inc. | System and process for providing improved database interfacing using query objects |
US6125363A (en) * | 1998-03-30 | 2000-09-26 | Buzzeo; Eugene | Distributed, multi-user, multi-threaded application development method |
US6157965A (en) * | 1998-02-27 | 2000-12-05 | Intel Corporation | System and method for binding a virtual device driver to a network driver interface |
US6223172B1 (en) * | 1997-10-31 | 2001-04-24 | Nortel Networks Limited | Address routing using address-sensitive mask decimation scheme |
US6314501B1 (en) * | 1998-07-23 | 2001-11-06 | Unisys Corporation | Computer system and method for operating multiple operating systems in different partitions of the computer system and for allowing the different partitions to communicate with one another through shared memory |
US6421742B1 (en) * | 1999-10-29 | 2002-07-16 | Intel Corporation | Method and apparatus for emulating an input/output unit when transferring data over a network |
US6473803B1 (en) * | 1997-06-02 | 2002-10-29 | Unisys Corporation | Virtual LAN interface for high-speed communications between heterogeneous computer systems |
US20040202166A1 (en) * | 1994-06-08 | 2004-10-14 | Hughes Electronics Corporation | Network system with TCP/IP protocol spoofing |
US6907042B1 (en) * | 1999-05-18 | 2005-06-14 | Fujitsu Limited | Packet processing device |
US6988150B2 (en) * | 2002-05-06 | 2006-01-17 | Todd Matters | System and method for eventless detection of newly delivered variable length messages from a system area network |
US7346075B1 (en) * | 2000-02-25 | 2008-03-18 | International Business Machines Corporation | Portable networking interface method and apparatus for distributed switching system |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4908823A (en) * | 1988-01-29 | 1990-03-13 | Hewlett-Packard Company | Hybrid communications link adapter incorporating input/output and data communications technology |
US5307413A (en) | 1991-07-19 | 1994-04-26 | Process Software Corporation | Method and apparatus for adding data compression and other services in a computer network |
US5630061A (en) | 1993-04-19 | 1997-05-13 | International Business Machines Corporation | System for enabling first computer to communicate over switched network with second computer located within LAN by using media access control driver in different modes |
US5655148A (en) | 1994-05-27 | 1997-08-05 | Microsoft Corporation | Method for automatically configuring devices including a network adapter without manual intervention and without prior configuration information |
IL110537A (en) * | 1994-08-01 | 1998-01-04 | 3Com Corp | Network switch |
US6948070B1 (en) * | 1995-02-13 | 2005-09-20 | Intertrust Technologies Corporation | Systems and methods for secure transaction management and electronic rights protection |
US5812767A (en) | 1995-07-28 | 1998-09-22 | International Business Machines Corporation | System for user registering an address resolution routine to provide address resolution procedure which is used by data link provider interface for resolving address conflicts |
US6516355B1 (en) * | 1995-11-08 | 2003-02-04 | Adc Newnet, Inc. | Methods and apparatus for controlling digital communications switching equipment |
US5684800A (en) | 1995-11-15 | 1997-11-04 | Cabletron Systems, Inc. | Method for establishing restricted broadcast groups in a switched network |
US5826030A (en) * | 1995-11-30 | 1998-10-20 | Excel Switching Corporation | Telecommunication switch having a universal API with a single call processing message including user-definable data and response message each having a generic format |
US5822520A (en) | 1995-12-26 | 1998-10-13 | Sun Microsystems, Inc. | Method and apparatus for building network test packets |
JP3650672B2 (en) | 1996-04-30 | 2005-05-25 | 本田技研工業株式会社 | Control device for internal combustion engine for vehicle |
US6118776A (en) * | 1997-02-18 | 2000-09-12 | Vixel Corporation | Methods and apparatus for fiber channel interconnection of private loop devices |
DE19732011A1 (en) * | 1997-07-25 | 1999-01-28 | Abb Patent Gmbh | Process for the location-transparent exchange of process data |
US6118768A (en) * | 1997-09-26 | 2000-09-12 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem utilizing browser-based configuration with adaptation of network parameters |
US6081508A (en) * | 1998-02-25 | 2000-06-27 | Indus River Networks, Inc. | Remote computer communication |
US6044415A (en) * | 1998-02-27 | 2000-03-28 | Intel Corporation | System for transferring I/O data between an I/O device and an application program's memory in accordance with a request directly over a virtual connection |
US6445715B1 (en) * | 1998-08-27 | 2002-09-03 | Cisco Technology, Inc. | Dynamic trunk protocol |
US6202106B1 (en) * | 1998-09-09 | 2001-03-13 | Xilinx, Inc. | Method for providing specific knowledge of a structure of parameter blocks to an intelligent direct memory access controller |
US6738818B1 (en) * | 1999-12-27 | 2004-05-18 | Intel Corporation | Centralized technique for assigning I/O controllers to hosts in a cluster |
US20030099254A1 (en) * | 2000-03-03 | 2003-05-29 | Richter Roger K. | Systems and methods for interfacing asynchronous and non-asynchronous data media |
US7107359B1 (en) * | 2000-10-30 | 2006-09-12 | Intel Corporation | Host-fabric adapter having hardware assist architecture and method of connecting a host system to a channel-based switched fabric in a data network |
US7042842B2 (en) * | 2001-06-13 | 2006-05-09 | Computer Network Technology Corporation | Fiber channel switch |
US20030202510A1 (en) * | 2002-04-26 | 2003-10-30 | Maxxan Systems, Inc. | System and method for scalable switch fabric for computer network |
US7944920B2 (en) * | 2002-06-11 | 2011-05-17 | Pandya Ashish A | Data processing system using internet protocols and RDMA |
US7275103B1 (en) * | 2002-12-18 | 2007-09-25 | Veritas Operating Corporation | Storage path optimization for SANs |
US7046668B2 (en) * | 2003-01-21 | 2006-05-16 | Pettey Christopher J | Method and apparatus for shared I/O in a load/store fabric |
KR100568178B1 (en) * | 2003-07-18 | 2006-04-05 | 삼성전자주식회사 | Gateway unit and control method thereof |
US7743197B2 (en) * | 2006-05-11 | 2010-06-22 | Emulex Design & Manufacturing Corporation | System and method for virtualizing PCIe devices |
-
2000
- 2000-02-25 US US09/513,518 patent/US7346075B1/en not_active Expired - Lifetime
-
2007
- 2007-05-23 US US11/752,476 patent/US7480311B2/en not_active Expired - Lifetime
- 2007-08-23 US US11/844,106 patent/US7711001B2/en not_active Expired - Lifetime
-
2008
- 2008-11-03 US US12/263,687 patent/US20090046600A1/en not_active Abandoned
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5732338A (en) * | 1987-07-27 | 1998-03-24 | Prs Corporation | Broadcast receiver capable of autonomous format-scanning, program identification and searching |
US20040202166A1 (en) * | 1994-06-08 | 2004-10-14 | Hughes Electronics Corporation | Network system with TCP/IP protocol spoofing |
US6031843A (en) * | 1996-11-21 | 2000-02-29 | Alcatel Data Networks Inc. | Digital communications switching fabric |
US6032193A (en) * | 1997-03-20 | 2000-02-29 | Niobrara Research And Development Corporation | Computer system having virtual circuit address altered by local computer to switch to different physical data link to increase data transmission bandwidth |
US5970069A (en) * | 1997-04-21 | 1999-10-19 | Lsi Logic Corporation | Single chip remote access processor |
US6473803B1 (en) * | 1997-06-02 | 2002-10-29 | Unisys Corporation | Virtual LAN interface for high-speed communications between heterogeneous computer systems |
US6076092A (en) * | 1997-08-19 | 2000-06-13 | Sun Microsystems, Inc. | System and process for providing improved database interfacing using query objects |
US6223172B1 (en) * | 1997-10-31 | 2001-04-24 | Nortel Networks Limited | Address routing using address-sensitive mask decimation scheme |
US6157965A (en) * | 1998-02-27 | 2000-12-05 | Intel Corporation | System and method for binding a virtual device driver to a network driver interface |
US6125363A (en) * | 1998-03-30 | 2000-09-26 | Buzzeo; Eugene | Distributed, multi-user, multi-threaded application development method |
US6314501B1 (en) * | 1998-07-23 | 2001-11-06 | Unisys Corporation | Computer system and method for operating multiple operating systems in different partitions of the computer system and for allowing the different partitions to communicate with one another through shared memory |
US6907042B1 (en) * | 1999-05-18 | 2005-06-14 | Fujitsu Limited | Packet processing device |
US6421742B1 (en) * | 1999-10-29 | 2002-07-16 | Intel Corporation | Method and apparatus for emulating an input/output unit when transferring data over a network |
US7346075B1 (en) * | 2000-02-25 | 2008-03-18 | International Business Machines Corporation | Portable networking interface method and apparatus for distributed switching system |
US6988150B2 (en) * | 2002-05-06 | 2006-01-17 | Todd Matters | System and method for eventless detection of newly delivered variable length messages from a system area network |
Also Published As
Publication number | Publication date |
---|---|
US7480311B2 (en) | 2009-01-20 |
US7711001B2 (en) | 2010-05-04 |
US20070286096A1 (en) | 2007-12-13 |
US20070245360A1 (en) | 2007-10-18 |
US7346075B1 (en) | 2008-03-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7480311B2 (en) | Portable networking interface method for distributed switching system | |
JP3253863B2 (en) | Method of communicating maintenance information to remote device and apparatus for receiving maintenance information | |
JP4885413B2 (en) | Local addressing of mobile units in a WLAN by addressing multicast packets | |
US6850989B1 (en) | Method and apparatus for automatically configuring a network switch | |
JP5792894B2 (en) | Port expansion topology information acquisition method, system, control bridge, and uplink port processing method and system | |
US6880158B1 (en) | Network processor services architecture that is platform and operating system independent | |
WO2001018977A2 (en) | Integrated circuit switch with embedded processor | |
US20090147677A1 (en) | System, method, and apparatus for load-balancing to a plurality of ports | |
Tsutsui et al. | YARDS: FPGA/MPU Hybrid Architecture for Telecommunication Data Processing | |
CN111666242A (en) | Multi-channel communication system based on FT platform LPC bus | |
CN101207924A (en) | Method for processing multi-user connections in high speed grouped data terminal | |
US6965911B1 (en) | Efficiently exporting local device access onto a system area network using a direct-call interface | |
CN108599999A (en) | The network of OVS and Linux bridge is disposed in a kind of SDN new networks | |
CN108848098A (en) | A kind of the communication channel management method and system of embedded type terminal equipment | |
US7130948B2 (en) | Flexible interrupt handling methods for optical networking apparatuses with multiple multi-protocol optical networking modules | |
CN105049358A (en) | Virtual forwarding platform of SDN (Software Defined Network) and communication method thereof | |
US20040226016A1 (en) | Apparatus and method for sharing resources in a real-time processing system | |
US6005858A (en) | Telecommunications switching system | |
CN100441013C (en) | Apparatus and method for testing operating and maintaining functions of Iub interface of base station in communication system | |
Chanson et al. | Design and implementation of a Ferry Clip test system | |
Švéda | Routers and bridges for small area network interconnection | |
KR100209360B1 (en) | B-isdn interfacing apparatus providing intelligent device driver | |
KR950006567B1 (en) | Interfacing method of protocol management and operation system for packet switching function | |
Cheah et al. | Implementing manufacturing message specification services and protocol using iso development environment | |
KR100606087B1 (en) | Queue event processing method of inverse multiplexing over atm access apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |