US9270586B2 - Method for abstracting datapath hardware elements - Google Patents
Method for abstracting datapath hardware elements Download PDFInfo
- Publication number
- US9270586B2 US9270586B2 US13/628,152 US201213628152A US9270586B2 US 9270586 B2 US9270586 B2 US 9270586B2 US 201213628152 A US201213628152 A US 201213628152A US 9270586 B2 US9270586 B2 US 9270586B2
- Authority
- US
- United States
- Prior art keywords
- tables
- virtual
- data
- network element
- hardware elements
- 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.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
Definitions
- This application relates to network elements and, more particularly, to a method for abstracting datapath hardware elements.
- Data communication networks may include various switches, nodes, routers, and other devices coupled to and configured to pass data to one another. These devices will be referred to herein as “network elements”. Data is communicated through the data communication network by passing protocol data units, such as frames, packets, cells, or segments, between the network elements by utilizing one or more communication links. A particular protocol data unit may be handled by multiple network elements and cross multiple communication links as it travels between its source and its destination over the network.
- protocol data units such as frames, packets, cells, or segments
- Network elements are designed to handle packets of data efficiently, to minimize the amount of delay associated with transmission of the data on the network. Conventionally, this is implemented by using hardware in a data plane of the network element to forward packets of data, while using software in a control plane of the network element to configure the network element to cooperate with other network elements on the network.
- a network element may include a routing process, which runs in the control plane, that enables the network element to have a synchronized view of the network topology. Forwarding state, computed using this network topology is then programmed into the data plane to enable the network element to forward packets of data across the network. Multiple processes may be running in the control plane to enable the network element to interact with other network elements on the network and forward data packets on the network.
- the control plane programs the hardware in the dataplane to enable the dataplane to be adjusted to properly handle traffic.
- the data plane includes ASICs, FPGAs, and other hardware elements designed to receive packets of data, perform lookup operations on specified fields of packet headers, and make forwarding decisions as to how the packet should be transmitted on the network. Lookup operations are typically implemented using tables and registers containing entries populated by the control plane.
- Drivers are used to abstract the data plane hardware elements from the control plane applications and provide a set of functions which the applications may use to program the hardware implementing the dataplane.
- Example driver calls may include “add route”, “delete route”, and hundreds of other instructions which enable the applications to instruct the driver to adjust the hardware to cause the network element to exhibit desired behavior on the network.
- the driver takes the instructions received from the control plane and implements the instructions by setting values in data registers and physical tables that are used by the hardware to control operation of the hardware. Since the driver code is specifically created to translate instructions from the applications to updates to the hardware, any changes to the hardware requires that the driver code be updated. Further, changes to the hardware may also require changes to the application code. For example, adding functionality to the hardware may require the application to be adjusted to allow the application to output instructions to the driver layer to take advantage of the new functionality. Likewise, the driver may need to be adjusted to implement the new instructions from the application to enable the new functionality to be accessed. Implementing changes to the driver code and/or to the application code increases development cost, since any time this code is changed it needs to be debugged to check for problems. This not only costs money, but also increases the amount of time required to bring the newly configured product to market.
- a table based abstraction layer is interposed between applications and the packet forwarding hardware driver layer. All behavior and configuration of packet forwarding to be implemented in the hardware layer is articulated as fields in tables of the table based abstraction layer, and the higher level application software interacts with the hardware through the creation of and insertion and deletion of elements in these tables.
- the structure of the tables in the abstraction layer has no direct functional meaning to the hardware, but rather the tables of the table based abstraction layer simply exist to receive data to be inserted by the applications into the forwarding hardware.
- Information from the tables is extracted by the packet forwarding hardware driver layer and used to populate physical offset tables that may then be installed into the registers and physical tables utilized by the hardware to perform packet forwarding operations.
- FIG. 1 is a functional block diagram of an example network
- FIG. 2 is a functional block diagram of an example network element
- FIGS. 3 and 4 are functional block diagrams showing processing environments of example network elements.
- FIG. 1 illustrates an example of a network 10 in which a plurality of network elements 12 such as switches and routers are interconnected by links 14 to transmit packets of data. As network elements 12 receive packets they make forwarding decisions to enable the packets of data to be forwarded on the network toward their intended destinations.
- network elements 12 receive packets they make forwarding decisions to enable the packets of data to be forwarded on the network toward their intended destinations.
- FIG. 2 shows one example network element, although the particular manner in which the network element is constructed may vary significantly from that shown in FIG. 2 .
- the network element 12 includes one or more control processes 200 associated with control plane software applications that are configured to control operation of the network element on the network 10 .
- Example control processes may include processes associated with application software 202 and platform software 204 .
- Application software includes routing software (e.g. shortest path bridging or link state routing protocol software), network operation administration and management software, interface creation/management software, and other software designed to control how the network element interacts with other network elements on the network.
- Platform software is software designed to control components of the hardware.
- platform software components may include a port manager, chassis manager, fabric manager, and other software configured to control aspects of the hardware elements.
- the control processes 200 are used to configure operation of the hardware components (data plane) of the network element to enable the network element to handle the rapid transmission of packets of data.
- the data plane in the illustrated embodiment, includes ports (labeled A1-A4, B1-B4, C1-C4, D1-D4) connected to physical media to receive and transmit data.
- the physical media may be implemented using a number of technologies, including fiber optic cables, electrical wires, or implemented using one or more wireless communication standards.
- ports are supported on line cards 210 to facilitate easy port replacement, although other ways of implementing the ports may be used as well.
- the line cards 210 may have processing capabilities implemented, for example, using microprocessors 220 or other hardware configured to format the packets, perform pre-classification of the packets, and perform other processes on packets of data received via the physical media.
- the data plane further includes one or more Network Processing Units (NPU) 230 and a switch fabric 240 .
- NPU Network Processing Unit
- the NPU and switch fabric enable lookup operations to be implemented for packets of data and enable packets of data to be forwarded to selected sets of ports to allow the network element to forward network traffic toward its destination on the network.
- Each of the line card processors 220 , network processing unit 230 , and switch fabric 240 may be configured to access physical tables and registers implemented in memory 250 in connection with making forwarding decisions.
- the line cards 210 , microprocessor 220 , network processing units 230 , switch fabric 240 , and memories 250 collectively implement the data plane of the network element 12 which enables the network element to receive packets of data, make forwarding decisions, and forward the packets of data on network 10 .
- Functionality of the various components of the data plane may be divided between the various components in any desired manner, and the invention is not limited to a network element having the specific data plane architecture illustrated in FIG. 2 .
- FIG. 3 illustrates an example processing environment implemented in network element 12 .
- hardware modifications resulting in changes in the configuration of the network element data plane may be accommodated by implementing a table based abstraction layer 310 intermediate applications 300 and packet forwarding hardware elements 320 .
- the applications instead of implementing a functional based driver API in which applications specific functions to be implemented by the driver, the applications instead output data to be inserted and retrieved from a set of virtual tables 345 .
- the interaction with the applications is thus simplified to through the use of a table based abstraction layer between the application and packet forwarding hardware element driver layer.
- These tables are referred to herein as “virtual tables” since the syntax of the virtual tables is independent of the physical tables used by the data plane in connection with making forwarding decisions on packets of data.
- the component object layer forms a hardware driver which converts between virtual tables and physical tables.
- Use of the virtual tables as an interface to the driver insulates the applications from the underlying hardware changes.
- changes to the underlying hardware could require updates to the applications to allow the applications to access the changed hardware via API calls. For example, if a new function was enabled by changing the hardware, the application may need to be changed to use a new API call to access the new functionality.
- the processing environment illustrated in FIG. 3 operates in reverse, by allowing the applications to specify the output format, which is received by the table based abstraction layer and inserted into the virtual tables.
- the packet forwarding hardware element driver layer maps information from the virtual tables 345 to the format required by the underlying hardware to allow data to correctly be set into the tables 322 and register 324 used by the packet forwarding hardware elements to make packet forwarding decisions.
- FIG. 3 shows a high level view of an embodiment.
- API 330 enables applications 300 to interact with component object layer 340 which maps data from virtual tables 345 to physical tables 322 and registers 324 used by the packet forwarding hardware elements 320 to make packet forwarding decisions.
- table managers 350 convert virtual search table commands to virtual index table commands (discussed below).
- a heap manager 360 is provided to manage memory allocated for storage of data in virtual tables 345 .
- a configuration library 370 specifies the mapping to be used by the component object layer to enable the component object layer to map from virtual tables to the underlying tables and registers used by the hardware elements to make forwarding decisions.
- API 330 has a small set of commands, which enable SET, GET, and EVENT actions to be implemented on the virtual tables.
- Set commands are used by applications to write data to the virtual tables; Get commands are used by applications to read data from the virtual tables; and Event commands are used to notify the applications of occurrences.
- the applications are able to use a Get Index command to obtain a memory allocation from the heap manager and are able to use a Free Index command to release memory in the heap manager to allow the applications to request and release memory allocated to storing data in virtual tables.
- the applications are thus able to interact with the table based abstraction layer using a very small set of commands.
- the same small API set may be used to implement multiple functions. Further, changes to the functionality of the underlying hardware elements does not require changes to the API to enable the applications to access the new functionality. Hence, adding functionality to the hardware does not require changes at the application level. For example, instead of having an action based AIP “set route” and another action based API “set VPN” the application may implement both of these functions simply using a SET command to cause the new route data and the new VPN data to be inserted into the correct fields of the virtual tables.
- the component object layer 340 is configurable as described in greater detail in U.S. patent application entitled Self-Adapting Driver for Controlling Datapath Hardware Elements, filed on Sep. 27, 2012, the content of which is hereby incorporated herein by reference.
- This application describes an implementation in which methods and mapping implemented by the component object layer is specified by configuration library 370 to enable data set into the virtual tables to be to mapped physical tables and registers in the data plane used by the hardware 320 to make forwarding decisions.
- the component object layer has set of methods which interact with a configuration file to determine how fields of data in the virtual tables should be mapped to registers and data structures in the packet forwarding hardware elements.
- the component object layer causes data to be set into the hardware elements using known processes, e.g. via kernel driver or other known components. Kernel API/drivers and hardware are standard components which are implemented in a known manner and are not affected by implementation of the virtual table interface layer.
- FIG. 4 illustrates a functional block diagram of an embodiment of a processing environment of a network element according to an embodiment.
- applications 400 communicate with middleware 410 which converts application messages to messages to be passed to a table based abstraction layer 420 .
- Table based abstraction layer 420 includes a set of API function calls that completely abstracts the management of the data path infrastructure from the middleware and higher layers. This layer defines two virtual table types—namely virtual index tables 422 and virtual search tables 424 . The set of API function calls is optimized to perform well-defined operations on the tables.
- applications generate two types of messages—configuration messages which are used by applications for configuration purposes, and query messages which are used to retrieve information. Reply messages are expected by the application in response to a query message.
- the middle-ware may generate and transmit event notification messages to the application upon occurrence of a real time event within the middleware.
- a Virtual Index Table (VIT) 422 represents an abstraction of one or more physical tables. It includes one or more records where each record is associated with a unique Index.
- An index is a zero-based unsigned integer that is uniquely associated with a record in a virtual index table.
- a record is a virtual table unit of access. Each record is associated with a unique index and is a container for one or more attributes.
- the index may either come from the application or the application may request one from the heap manager using a get index instruction.
- Attributes are data structures that have the following properties: (1) identifier; (2) mask; and (3) value.
- An attribute may belong to one or more virtual tables and may be an index to another table, a key or a data field. The attribute ID uniquely identifies an attribute across all virtual tables.
- a Virtual Search Table has one or more records. Each record is associated with a unique index or search index. The record contains one or more attributes. A set of attributes have a key type and are referred to as key attributes. Adding a record to a virtual search table involves mapping the key attributes to a unique search index and storing the record at the search index. Deleting a record involves finding a record that matches the key and removing it from the search table.
- a virtual search table abstracts the functions that map the key to a search index. The mapping functions or search algorithms may be implemented in software, hardware, or both. Typical search algorithms include radix tree, AVL tree, hash table, Ternary Content Addressable Memory (TCAM), although other search algorithms may be used as well.
- the component object layer supports virtual index tables only. To enable virtual search tables to be accessed by the applications via API 330 , table manager 350 receive virtual search table API calls and translates the calls to a set of virtual index table instructions to be implemented by component object layer.
- the virtual tables are implemented using physical memory allocations such that the virtual tables are stored using data structures in memory implemented as physical tables.
- a physical table occupies a region of physical address space and contains one or more entries. An entry may span one or more contiguous physical memory locations.
- the physical table is specified by a base address, maximum number of entries, entry width, and entry stride (number of lines of memory occupied by each entry).
- An entry is one or more contiguous physical memory locations in a physical offset table. Entries can be either contiguous or sparse with fixed stride.
- the width of an entry represents the number of bits that actually exist in a physical table.
- the entry stride is the number of bytes that is added to the current physical table offset to access the next physical entry. The width of an entry is always less than or equal to the entry stride *8, where 8 represents the number of bits per one byte.
- the physical table is accessed using an offset from its base address.
- An offset in this context, is a zero-based unsigned integer. Its value represents the number of bytes from the physical table base address to a specific entry. Each entry is associated with an offset relative to the physical table base address.
- a datapath management infrastructure layer 430 extracts information from the virtual tables and installs information from the virtual tables into physical tables at the hardware layer.
- the hardware layer includes the Kernel Application Program Interface (API)/drivers 440 , and actual hardware 450 .
- API Kernel Application Program Interface
- the datapath management infrastructure layer may be implemented to include a driver 432 , implemented as component object layer in FIG. 3 , that is configured to map information from the virtual tables 422 , 424 , to physical tables implemented in the hardware 450 .
- the data path management infrastructure layer includes a representation of the data path hardware tables 434 . As data is written to the data path hardware tables, the data path management infrastructure layer passes commands to the Kernel API to cause the kernel drivers to install the correct entries into the actual physical tables utilized by the hardware.
- the data path management infrastructure 430 also includes virtual table managers 436 , and heap manager 438 .
- an application that needs to affect operation of how the data plane handles a class of traffic will output information associated with the class of traffic using a virtual table set command. For example, if traffic associated with a particular destination address and Virtual Local Area Network Identifier (VID) is to be transported over a particular Virtual Private Network, the application may use a virtual table set command to cause the destination address (DA) and VID to be written to fields of the virtual tables.
- VIP Virtual Local Area Network Identifier
- the driver 432 maps the DA/VID to appropriate fields of the data path hardware tables 434 , and the kernel API/drivers 440 install the information from the data path hardware tables to registers and memories 250 to allow the data path hardware to correctly cause traffic associated with the DA/VID to be forwarded on the VPN.
- the API supports the Virtual Index Table instructions set forth below in Table I:
- the SET_ATTR command includes the virtual table ID, Index, and Attributes, and is used to set data into an Index Table GET_ATTR
- the GET_ATTR command includes the virtual table ID and Index, and is used to retrieve the value of the attributes stored at the Index GET_INDEX
- the GET_INDEX command is used if the index to the virtual table is not visible to the application. It dynamically allocates an index which is then used by the SET_ATTR command
- the API also supports the Virtual Search Table instructions set forth below in Table II:
- ADD_OR_UPDATE_RECORD includes the virtual table ID, key, and attribute list from the application to the virtual table, and is used to set data into a search table.
- DELETE_RECORD The DELETE_RECORD command includes the virtual table ID and key, and is used to remove a record from the search table.
- GET_ATTR The GET_ATTR command includes the virtual table ID and key, and is used to retrieve the value of the attributes stored at the record
- QUERY QUERY commands such as QUERY(key) and QUERY(value) are also supported. QUERY(key) will return a range of values, and QUERY(value) is used to return a range of records.
- the table managers 350 are provided to convert virtual search table commands into virtual index table commands such that the physical implementation of the virtual tables is simplified.
- the functions described herein may be embodied as a software program implemented in control logic on a processor on the network element or may be configured as a FPGA or other processing unit on the network element.
- the control logic in this embodiment may be implemented as a set of program instructions that are stored in a computer readable memory within the network element and executed on a microprocessor on the network element.
- ASIC Application Specific Integrated Circuit
- FPGA Field Programmable Gate Array
- Programmable logic can be fixed temporarily or permanently in a tangible non-transitory computer-readable medium such as a random access memory, cache memory, read-only memory chip, a computer memory, a disk, or other storage medium. All such embodiments are intended to fall within the scope of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
TABLE I | |
Instruction | Function |
SET_ATTR | The SET_ATTR command includes the virtual table ID, |
Index, and Attributes, and is used to set data into an | |
Index Table | |
GET_ATTR | The GET_ATTR command includes the virtual table ID |
and Index, and is used to retrieve the value of the | |
attributes stored at the Index | |
GET_INDEX | The GET_INDEX command is used if the index to the |
virtual table is not visible to the application. It | |
dynamically allocates an index which is then used by | |
the SET_ATTR command | |
TABLE II | |
Instruction | Function |
ADD_OR_UPDATE_RECORD | The ADD_OR_UPDATE_RECORD |
command includes the virtual table ID, | |
key, and attribute list from the application | |
to the virtual table, and is used to set data | |
into a search table. | |
DELETE_RECORD | The DELETE_RECORD command |
includes the virtual table ID and key, and | |
is used to remove a record from the search | |
table. | |
GET_ATTR | The GET_ATTR command includes the |
virtual table ID and key, and is used to | |
retrieve the value of the attributes stored | |
at the record | |
QUERY | QUERY commands, such as |
QUERY(key) and QUERY(value) are also | |
supported. QUERY(key) will return a | |
range of values, and QUERY(value) is | |
used to return a range of records. | |
As noted above, in one embodiment the
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/628,152 US9270586B2 (en) | 2012-09-27 | 2012-09-27 | Method for abstracting datapath hardware elements |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/628,152 US9270586B2 (en) | 2012-09-27 | 2012-09-27 | Method for abstracting datapath hardware elements |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140086240A1 US20140086240A1 (en) | 2014-03-27 |
US9270586B2 true US9270586B2 (en) | 2016-02-23 |
Family
ID=50338796
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/628,152 Active 2033-07-04 US9270586B2 (en) | 2012-09-27 | 2012-09-27 | Method for abstracting datapath hardware elements |
Country Status (1)
Country | Link |
---|---|
US (1) | US9270586B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10313495B1 (en) | 2017-07-09 | 2019-06-04 | Barefoot Networks, Inc. | Compiler and hardware interactions to remove action dependencies in the data plane of a network forwarding element |
US10516626B1 (en) * | 2016-03-16 | 2019-12-24 | Barefoot Networks, Inc. | Generating configuration data and API for programming a forwarding element |
US10721167B1 (en) | 2017-10-09 | 2020-07-21 | Barefoot Networks, Inc. | Runtime sharing of unit memories between match tables in a network forwarding element |
US20230214388A1 (en) * | 2021-12-31 | 2023-07-06 | Fortinet, Inc. | Generic tree policy search optimization for high-speed network processor configuration |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9986434B2 (en) * | 2014-04-30 | 2018-05-29 | Avago Technologies General Ip (Singapore) Pte. Ltd. | System for accelerated network route update through exclusive access to routing tables |
US20170085500A1 (en) * | 2015-09-18 | 2017-03-23 | Pluribus Networks, Inc. | Streamlined processing in a network switch of network packets in a spliced connection |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030009584A1 (en) * | 2001-06-20 | 2003-01-09 | International Business Machines Corporation | Robust NP-based data forwarding techniques that tolerate failure of control-based applications |
US20030126195A1 (en) * | 2000-05-20 | 2003-07-03 | Reynolds Daniel A. | Common command interface |
US20040249803A1 (en) * | 2003-06-05 | 2004-12-09 | Srinivasan Vankatachary | Architecture for network search engines with fixed latency, high capacity, and high throughput |
US20110274035A1 (en) * | 2010-05-04 | 2011-11-10 | Cisco Technology, Inc. | Routing to the Access Layer to Support Mobility of Internet Protocol Devices |
-
2012
- 2012-09-27 US US13/628,152 patent/US9270586B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030126195A1 (en) * | 2000-05-20 | 2003-07-03 | Reynolds Daniel A. | Common command interface |
US20030009584A1 (en) * | 2001-06-20 | 2003-01-09 | International Business Machines Corporation | Robust NP-based data forwarding techniques that tolerate failure of control-based applications |
US20040249803A1 (en) * | 2003-06-05 | 2004-12-09 | Srinivasan Vankatachary | Architecture for network search engines with fixed latency, high capacity, and high throughput |
US20110274035A1 (en) * | 2010-05-04 | 2011-11-10 | Cisco Technology, Inc. | Routing to the Access Layer to Support Mobility of Internet Protocol Devices |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10516626B1 (en) * | 2016-03-16 | 2019-12-24 | Barefoot Networks, Inc. | Generating configuration data and API for programming a forwarding element |
US10313495B1 (en) | 2017-07-09 | 2019-06-04 | Barefoot Networks, Inc. | Compiler and hardware interactions to remove action dependencies in the data plane of a network forwarding element |
US10764176B1 (en) | 2017-07-09 | 2020-09-01 | Barefoot Networks, Inc. | Compiler and hardware interactions to reuse register fields in the data plane of a network forwarding element |
US10805437B2 (en) | 2017-07-09 | 2020-10-13 | Barefoot Networks, Inc. | Compiler and hardware interactions to remove action dependencies in the data plane of a network forwarding element |
US10721167B1 (en) | 2017-10-09 | 2020-07-21 | Barefoot Networks, Inc. | Runtime sharing of unit memories between match tables in a network forwarding element |
US20230214388A1 (en) * | 2021-12-31 | 2023-07-06 | Fortinet, Inc. | Generic tree policy search optimization for high-speed network processor configuration |
Also Published As
Publication number | Publication date |
---|---|
US20140086240A1 (en) | 2014-03-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11929945B2 (en) | Managing network traffic in virtual switches based on logical port identifiers | |
US9270586B2 (en) | Method for abstracting datapath hardware elements | |
US9246802B2 (en) | Management of routing tables shared by logical switch partitions in a distributed network switch | |
US20160205019A1 (en) | Port extender | |
JP7208008B2 (en) | Systems and methods for providing a programmable packet classification framework for use in network devices | |
CN113326228B (en) | Message forwarding method, device and equipment based on remote direct data storage | |
US20170041223A1 (en) | Transfer device and transfer system | |
US9197539B2 (en) | Multicast miss notification for a distributed network switch | |
US8989193B2 (en) | Facilitating insertion of device MAC addresses into a forwarding database | |
US20150131666A1 (en) | Apparatus and method for transmitting packet | |
WO2019185051A1 (en) | Integrated flow table-based packet forwarding method and device | |
US10084613B2 (en) | Self adapting driver for controlling datapath hardware elements | |
CN112887229B (en) | Session information synchronization method and device | |
CN111327509B (en) | Information updating method and device | |
US9596138B2 (en) | Smart dumping of network switch forwarding database | |
JP6079348B2 (en) | Switch device, switch device control method, and network system | |
CN104702508A (en) | Method and system for dynamically updating table items | |
JP6677052B2 (en) | Communication management device, communication management method and program | |
CN114448886A (en) | Flow table processing method and device | |
US20200319875A1 (en) | Dynamic runtime programming of hardware tables | |
US11314414B2 (en) | Methods, devices, and computer program products for storage management | |
US20220231961A1 (en) | Updating flow cache information for packet processing | |
CN116366530A (en) | Stream table aging method and device, computer equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:029608/0256 Effective date: 20121221 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., P Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:029608/0256 Effective date: 20121221 |
|
AS | Assignment |
Owner name: AVAYA INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ASSARPOUR, HAMID;REEL/FRAME:029802/0185 Effective date: 20121203 |
|
AS | Assignment |
Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639 Effective date: 20130307 Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639 Effective date: 20130307 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:AVAYA INC.;AVAYA INTEGRATED CABINET SOLUTIONS INC.;OCTEL COMMUNICATIONS CORPORATION;AND OTHERS;REEL/FRAME:041576/0001 Effective date: 20170124 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT;ASSIGNOR:EXTREME NETWORKS, INC.;REEL/FRAME:043200/0614 Effective date: 20170714 |
|
AS | Assignment |
Owner name: EXTREME NETWORKS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AVAYA INC.;AVAYA COMMUNICATION ISRAEL LTD;AVAYA HOLDINGS LIMITED;REEL/FRAME:043569/0047 Effective date: 20170714 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT;ASSIGNOR:EXTREME NETWORKS, INC.;REEL/FRAME:044639/0300 Effective date: 20171027 |
|
AS | Assignment |
Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION), CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:044891/0801 Effective date: 20171128 Owner name: VPNET TECHNOLOGIES, INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INTEGRATED CABINET SOLUTIONS INC., CALIFORNI Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044893/0531 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:045012/0666 Effective date: 20171128 |
|
AS | Assignment |
Owner name: BANK OF MONTREAL, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:EXTREME NETWORKS, INC.;REEL/FRAME:046050/0546 Effective date: 20180501 Owner name: EXTREME NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:046051/0775 Effective date: 20180501 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: BANK OF MONTREAL, NEW YORK Free format text: AMENDED SECURITY AGREEMENT;ASSIGNORS:EXTREME NETWORKS, INC.;AEROHIVE NETWORKS, INC.;REEL/FRAME:064782/0971 Effective date: 20230818 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |