US20190044809A1 - Technologies for managing a flexible host interface of a network interface controller - Google Patents

Technologies for managing a flexible host interface of a network interface controller Download PDF

Info

Publication number
US20190044809A1
US20190044809A1 US15/833,523 US201715833523A US2019044809A1 US 20190044809 A1 US20190044809 A1 US 20190044809A1 US 201715833523 A US201715833523 A US 201715833523A US 2019044809 A1 US2019044809 A1 US 2019044809A1
Authority
US
United States
Prior art keywords
descriptor
message
dma
host interface
compute device
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
Application number
US15/833,523
Other languages
English (en)
Inventor
Thomas E. Willis
Brad Burres
Amit Kumar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Priority to US15/833,523 priority Critical patent/US20190044809A1/en
Assigned to INTEL CORPORATION reassignment INTEL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BURRES, BRAD, KUMAR, AMIT, WILLIS, THOMAS E.
Priority to DE102018212479.5A priority patent/DE102018212479A1/de
Priority to CN202110870167.3A priority patent/CN113806260B/zh
Priority to CN201811004869.8A priority patent/CN109426633A/zh
Priority to CN202311445788.2A priority patent/CN117725004A/zh
Publication of US20190044809A1 publication Critical patent/US20190044809A1/en
Priority to US17/344,253 priority patent/US11843691B2/en
Priority to US18/241,748 priority patent/US20230412365A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163—Interprocessor communication
    • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3442—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for planning or managing the needed capacity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023—Free address space management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/06—Addressing a physical block of locations, e.g. base addressing, module addressing, memory dedication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/06—Addressing a physical block of locations, e.g. base addressing, module addressing, memory dedication
    • G06F12/0607—Interleaved addressing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/14—Protection against unauthorised use of memory or access to memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/16—Handling requests for interconnection or transfer for access to memory bus
    • G06F13/1605—Handling requests for interconnection or transfer for access to memory bus based on arbitration
    • G06F13/1652—Handling requests for interconnection or transfer for access to memory bus based on arbitration in a multiprocessor architecture
    • G06F13/1663—Access to shared memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/16—Handling requests for interconnection or transfer for access to memory bus
    • G06F13/1668—Details of memory controller
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4063—Device-to-bus coupling
    • G06F13/4068—Electrical coupling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/161—Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163—Interprocessor communication
    • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • G06F15/17306—Intercommunication techniques
    • G06F15/17331—Distributed shared memory [DSM], e.g. remote direct memory access [RDMA]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/76—Architectures of general purpose stored program computers
    • G06F15/78—Architectures of general purpose stored program computers comprising a single central processing unit
    • G06F15/7867—Architectures of general purpose stored program computers comprising a single central processing unit with reconfigurable architecture
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/119—Details of migration of file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/221—Column-oriented storage; Management thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2228—Indexing structures
    • G06F16/2237—Vectors, bitmaps or matrices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2228—Indexing structures
    • G06F16/2255—Hash tables
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2453—Query optimisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24553—Query execution of query operations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/248—Presentation of query results
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G06F16/9014—Indexing; Data structures therefor; Storage structures hash tables
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • G06F3/0611—Improving I/O performance in relation to response time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061—Improving I/O performance
    • G06F3/0613—Improving I/O performance in relation to throughput
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0632—Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/0644—Management of space entities, e.g. partitions, extents, pools
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647—Migration mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/065—Replication mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662—Virtualisation aspects
    • G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0673—Single storage device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0685—Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/30—Circuit design
    • G06F30/34—Circuit design for reconfigurable circuits, e.g. field programmable gate arrays [FPGA] or programmable logic devices [PLD]
    • 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/22—Microcontrol or microprogram arrangements
    • G06F9/28—Enhancement of operational speed, e.g. by using several microcontrol devices operating in parallel
    • 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
    • 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/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • 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/44—Arrangements for executing specific programs
    • G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4494—Execution paradigms, e.g. implementations of programming paradigms data driven
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5022—Mechanisms to release resources
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • G06F9/5088—Techniques for rebalancing the load in a distributed system involving task migration
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/02—Detection or location of defective auxiliary circuits, e.g. defective refresh counters
    • G11C29/028—Detection or location of defective auxiliary circuits, e.g. defective refresh counters with adaption or trimming of parameters
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
    • G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
    • G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
    • G11C29/36—Data generation devices, e.g. data inverters
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
    • G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
    • G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
    • G11C29/38—Response verification devices
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
    • G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
    • G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
    • G11C29/44—Indication or identification of errors, e.g. for repair
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C8/00—Arrangements for selecting an address in a digital store
    • G11C8/12—Group selection circuits, e.g. for memory block selection, chip selection, array selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H04L41/5025—Ensuring fulfilment of SLA by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • 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/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H04L45/7453—Address table lookup; Address filtering using hashing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/11—Identifying congestion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/83—Admission control; Resource allocation based on usage prediction
    • 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/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H04L49/9005—Buffering arrangements using dynamic buffer space allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/12—Protocol engines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0005—Switch and router aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/14—Mounting supporting structure in casing or on frame or rack
    • H05K7/1485—Servers; Data center rooms, e.g. 19-inch computer racks
    • H05K7/1488—Cabinets therefor, e.g. chassis or racks or mechanical interfaces between blades and support structures
    • H05K7/1489—Cabinets therefor, e.g. chassis or racks or mechanical interfaces between blades and support structures characterized by the mounting of blades therein, e.g. brackets, rails, trays
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/14—Mounting supporting structure in casing or on frame or rack
    • H05K7/1485—Servers; Data center rooms, e.g. 19-inch computer racks
    • H05K7/1498—Resource management, Optimisation arrangements, e.g. configuration, identification, tracking, physical location
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/18—Construction of rack or frame
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/20—Modifications to facilitate cooling, ventilating, or heating
    • H05K7/20009—Modifications to facilitate cooling, ventilating, or heating using a gaseous coolant in electronic enclosures
    • H05K7/20209—Thermal management, e.g. fan control
    • H—ELECTRICITY
    • H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
    • H05K—PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
    • H05K7/00—Constructional details common to different types of electric apparatus
    • H05K7/20—Modifications to facilitate cooling, ventilating, or heating
    • H05K7/20709—Modifications to facilitate cooling, ventilating, or heating for server racks or cabinets; for data centers, e.g. 19-inch computer racks
    • H05K7/20718—Forced ventilation of a gaseous coolant
    • H05K7/20736—Forced ventilation of a gaseous coolant within cabinets for removing heat from server blades
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/10—Address translation
    • G06F12/1027—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
    • G06F12/1045—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB] associated with a data cache
    • G06F12/1054—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB] associated with a data cache the data cache being concurrently physically addressed
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/10—Address translation
    • G06F12/1027—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
    • G06F12/1045—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB] associated with a data cache
    • G06F12/1063—Address translation using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB] associated with a data cache the data cache being concurrently virtually addressed
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4004—Coupling between buses
    • G06F13/4022—Coupling between buses using switching circuits, e.g. switching matrix, connection or expansion network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163—Interprocessor communication
    • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • G06F15/1735—Network adapters, e.g. SCI, Myrinet
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2200/00—Indexing scheme relating to G06F1/04 - G06F1/32
    • G06F2200/20—Indexing scheme relating to G06F1/20
    • G06F2200/201—Cooling arrangements using cooling fluid
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/85—Active fault masking without idle spares
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/86—Event-based monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/885—Monitoring specific for caches
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5019—Workload prediction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/509—Offload
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1041—Resource optimization
    • G06F2212/1044—Space efficiency improvement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10—Providing a specific technical effect
    • G06F2212/1052—Security improvement
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/60—Details of cache memory
    • G06F2212/601—Reconfiguration of cache memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F2213/0026—PCI express
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F2213/0064—Latency reduction in handling transfers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F2213/38—Universal adapter
    • G06F2213/3808—Network interface controller
    • 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/44—Arrangements for executing specific programs
    • 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • 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/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5044—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering hardware capabilities
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5055—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering software capabilities, i.e. software resources associated or available to the machine
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N3/00—Computing arrangements based on biological models
    • G06N3/02—Neural networks
    • G06N3/06—Physical realisation, i.e. hardware implementation of neural networks, neurons or parts of neurons
    • G06N3/063—Physical realisation, i.e. hardware implementation of neural networks, neurons or parts of neurons using electronic means
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283—Price estimation or determination
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/142—Network analysis or design using statistical or mathematical methods
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/149—Network analysis or design for prediction of maintenance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/40—Constructional details, e.g. power supply, mechanical construction or backplane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • data is transmitted in the form of network packets between compute devices and/or device components at a rapid pace.
  • data is packetized into a network packet, which is transmitted by a network interface controller (NIC) of one network compute device and received by a NIC of another network compute device.
  • NIC network interface controller
  • the network packet is typically processed, classified, etc., and the payload is typically written to memory (e.g., cache, main memory, etc.).
  • the receiving NIC may then notify a host central processing unit (CPU) that the data is available for further processing.
  • CPU central processing unit
  • the NIC includes an interface configured to manage the communications between the host CPU and the NIC (e.g., via peripheral component interconnect express (PCI-e)).
  • PCI-e peripheral component interconnect express
  • the NIC can support various features, such as interrupts, direct memory access (DMA) interfaces to the host processors, support for multiple receive and transmit queues, partitioning into multiple logical interfaces, network traffic processing, offloading, etc.
  • the interface relies on one or more protocols for host software and NIC hardware integration (e.g., to manage messages/communications between host virtual machines (VMs) and physical NIC functions).
  • VMs virtual machines
  • NIC physical NIC functions
  • certain software interface languages may not be supported by a particular NIC, such as may be based on the NIC's vendor, model, etc.
  • FIG. 1 is a diagram of a conceptual overview of a data center in which one or more techniques described herein may be implemented according to various embodiments;
  • FIG. 2 is a diagram of an example embodiment of a logical configuration of a rack of the data center of FIG. 1 ;
  • FIG. 3 is a diagram of an example embodiment of another data center in which one or more techniques described herein may be implemented according to various embodiments;
  • FIG. 4 is a diagram of another example embodiment of a data center in which one or more techniques described herein may be implemented according to various embodiments;
  • FIG. 5 is a diagram of a connectivity scheme representative of link-layer connectivity that may be established among various sleds of the data centers of FIGS. 1, 3, and 4 ;
  • FIG. 6 is a diagram of a rack architecture that may be representative of an architecture of any particular one of the racks depicted in FIGS. 1-4 according to some embodiments;
  • FIG. 7 is a diagram of an example embodiment of a sled that may be used with the rack architecture of FIG. 6 ;
  • FIG. 8 is a diagram of an example embodiment of a rack architecture to provide support for sleds featuring expansion capabilities
  • FIG. 9 is a diagram of an example embodiment of a rack implemented according to the rack architecture of FIG. 8 ;
  • FIG. 10 is a diagram of an example embodiment of a sled designed for use in conjunction with the rack of FIG. 9 ;
  • FIG. 11 is a diagram of an example embodiment of a data center in which one or more techniques described herein may be implemented according to various embodiments;
  • FIG. 12 is a simplified block diagram of at least one embodiment of a compute device for managing a flexible host interface of a network interface controller (NIC) of the compute device;
  • NIC network interface controller
  • FIG. 13 is a simplified block diagram of at least one embodiment of an environment that may be established by the NIC of FIG. 12 ;
  • FIG. 14 is a simplified block diagram of at least one embodiment of an environment that may be established by a flexible host interface of the NIC of FIG. 13 ;
  • FIG. 15 is a simplified flow diagram of at least one embodiment of a method for generating descriptor(s) for a network packet that may be performed by a host CPU of the compute device of FIG. 12 ;
  • FIG. 16 is a simplified flow diagram of at least one embodiment of a method for notifying a traffic manager of the NIC of FIG. 13 receipt of descriptor(s) that may be performed by the flexible host interface of FIGS. 13 and 14 ;
  • FIG. 17 is a simplified flow diagram of at least one embodiment of a method for processing messages that may be performed by a symmetric multi-processing array of the flexible host interface of FIG. 14 ;
  • FIGS. 18A and 18B are a simplified communication flow diagram of at least one embodiment for processing network packets that may be performed by the flexible host interface of FIG. 14 ;
  • FIG. 19 is a simplified communication flow diagram of at least one embodiment for throttling the processing of outbound network packets that may be performed by a job manager of FIG. 14 .
  • references in the specification to “one embodiment,” “an embodiment,” “an illustrative embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • items included in a list in the form of “at least one A, B, and C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).
  • items listed in the form of “at least one of A, B, or C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).
  • the disclosed embodiments may be implemented, in some cases, in hardware, firmware, software, or any combination thereof.
  • the disclosed embodiments may also be implemented as instructions carried by or stored on a transitory or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors.
  • a machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or non-volatile memory, a media disc, or other media device).
  • FIG. 1 illustrates a conceptual overview of a data center 100 that may generally be representative of a data center or other type of computing network in/for which one or more techniques described herein may be implemented according to various embodiments.
  • data center 100 may generally contain a plurality of racks, each of which may house computing equipment comprising a respective set of physical resources.
  • data center 100 contains four racks 102 A to 102 D, which house computing equipment comprising respective sets of physical resources (PCRs) 105 A to 105 D.
  • PCRs physical resources
  • a collective set of physical resources 106 of data center 100 includes the various sets of physical resources 105 A to 105 D that are distributed among racks 102 A to 102 D.
  • Physical resources 106 may include resources of multiple types, such as—for example—processors, co-processors, accelerators, field programmable gate arrays (FPGAs), memory, and storage. The embodiments are not limited to these examples.
  • the illustrative data center 100 differs from typical data centers in many ways.
  • the circuit boards (“sleds”) on which components such as CPUs, memory, and other components are placed are designed for increased thermal performance
  • the sleds are shallower than typical boards. In other words, the sleds are shorter from the front to the back, where cooling fans are located. This decreases the length of the path that air must to travel across the components on the board.
  • the components on the sled are spaced further apart than in typical circuit boards, and the components are arranged to reduce or eliminate shadowing (i.e., one component in the air flow path of another component).
  • processing components such as the processors are located on a top side of a sled while near memory, such as DIMMs, are located on a bottom side of the sled.
  • near memory such as DIMMs
  • the components may operate at higher frequencies and power levels than in typical systems, thereby increasing performance.
  • the sleds are configured to blindly mate with power and data communication cables in each rack 102 A, 102 B, 102 C, 102 D, enhancing their ability to be quickly removed, upgraded, reinstalled, and/or replaced.
  • individual components located on the sleds such as processors, accelerators, memory, and data storage drives, are configured to be easily upgraded due to their increased spacing from each other.
  • the components additionally include hardware attestation features to prove their authenticity.
  • the data center 100 utilizes a single network architecture (“fabric”) that supports multiple other network architectures including Ethernet and Omni-Path.
  • the sleds in the illustrative embodiment, are coupled to switches via optical fibers, which provide higher bandwidth and lower latency than typical twisted pair cabling (e.g., Category 5, Category 5e, Category 6, etc.).
  • the data center 100 may, in use, pool resources, such as memory, accelerators (e.g., graphics accelerators, FPGAs, ASICs, etc.), and data storage drives that are physically disaggregated, and provide them to compute resources (e.g., processors) on an as needed basis, enabling the compute resources to access the pooled resources as if they were local.
  • the illustrative data center 100 additionally receives utilization information for the various resources, predicts resource utilization for different types of workloads based on past resource utilization, and dynamically reallocates the resources based on this information.
  • the racks 102 A, 102 B, 102 C, 102 D of the data center 100 may include physical design features that facilitate the automation of a variety of types of maintenance tasks.
  • data center 100 may be implemented using racks that are designed to be robotically-accessed, and to accept and house robotically-manipulatable resource sleds.
  • the racks 102 A, 102 B, 102 C, 102 D include integrated power sources that receive a greater voltage than is typical for power sources. The increased voltage enables the power sources to provide additional power to the components on each sled, enabling the components to operate at higher than typical frequencies.
  • FIG. 2 illustrates an exemplary logical configuration of a rack 202 of the data center 100 .
  • rack 202 may generally house a plurality of sleds, each of which may comprise a respective set of physical resources.
  • rack 202 houses sleds 204 - 1 to 204 - 4 comprising respective sets of physical resources 205 - 1 to 205 - 4 , each of which constitutes a portion of the collective set of physical resources 206 comprised in rack 202 .
  • rack 202 is representative of—for example—rack 102 A
  • physical resources 206 may correspond to the physical resources 105 A comprised in rack 102 A.
  • physical resources 105 A may thus be made up of the respective sets of physical resources, including physical storage resources 205 - 1 , physical accelerator resources 205 - 2 , physical memory resources 205 - 3 , and physical compute resources 205 - 5 comprised in the sleds 204 - 1 to 204 - 4 of rack 202 .
  • the embodiments are not limited to this example.
  • Each sled may contain a pool of each of the various types of physical resources (e.g., compute, memory, accelerator, storage).
  • robotically accessible and robotically manipulatable sleds comprising disaggregated resources, each type of resource can be upgraded independently of each other and at their own optimized refresh rate.
  • FIG. 3 illustrates an example of a data center 300 that may generally be representative of one in/for which one or more techniques described herein may be implemented according to various embodiments.
  • data center 300 comprises racks 302 - 1 to 302 - 32 .
  • the racks of data center 300 may be arranged in such fashion as to define and/or accommodate various access pathways.
  • the racks of data center 300 may be arranged in such fashion as to define and/or accommodate access pathways 311 A, 311 B, 311 C, and 311 D.
  • the presence of such access pathways may generally enable automated maintenance equipment, such as robotic maintenance equipment, to physically access the computing equipment housed in the various racks of data center 300 and perform automated maintenance tasks (e.g., replace a failed sled, upgrade a sled).
  • automated maintenance equipment such as robotic maintenance equipment
  • the dimensions of access pathways 311 A, 311 B, 311 C, and 311 D, the dimensions of racks 302 - 1 to 302 - 32 , and/or one or more other aspects of the physical layout of data center 300 may be selected to facilitate such automated operations. The embodiments are not limited in this context.
  • FIG. 4 illustrates an example of a data center 400 that may generally be representative of one in/for which one or more techniques described herein may be implemented according to various embodiments.
  • data center 400 may feature an optical fabric 412 .
  • Optical fabric 412 may generally comprise a combination of optical signaling media (such as optical cabling) and optical switching infrastructure via which any particular sled in data center 400 can send signals to (and receive signals from) each of the other sleds in data center 400 .
  • the signaling connectivity that optical fabric 412 provides to any given sled may include connectivity both to other sleds in a same rack and sleds in other racks. In the particular non-limiting example depicted in FIG.
  • data center 400 includes four racks 402 A to 402 D.
  • Racks 402 A to 402 D house respective pairs of sleds 404 A- 1 and 404 A- 2 , 404 B- 1 and 404 B- 2 , 404 C- 1 and 404 C- 2 , and 404 D- 1 and 404 D- 2 .
  • data center 400 comprises a total of eight sleds. Via optical fabric 412 , each such sled may possess signaling connectivity with each of the seven other sleds in data center 400 .
  • sled 404 A- 1 in rack 402 A may possess signaling connectivity with sled 404 A- 2 in rack 402 A, as well as the six other sleds 404 B- 1 , 404 B- 2 , 404 C- 1 , 404 C- 2 , 404 D- 1 , and 404 D- 2 that are distributed among the other racks 402 B, 402 C, and 402 D of data center 400 .
  • the embodiments are not limited to this example.
  • FIG. 5 illustrates an overview of a connectivity scheme 500 that may generally be representative of link-layer connectivity that may be established in some embodiments among the various sleds of a data center, such as any of example data centers 100 , 300 , and 400 of FIGS. 1, 3, and 4 .
  • Connectivity scheme 500 may be implemented using an optical fabric that features a dual-mode optical switching infrastructure 514 .
  • Dual-mode optical switching infrastructure 514 may generally comprise a switching infrastructure that is capable of receiving communications according to multiple link-layer protocols via a same unified set of optical signaling media, and properly switching such communications.
  • dual-mode optical switching infrastructure 514 may be implemented using one or more dual-mode optical switches 515 .
  • dual-mode optical switches 515 may generally comprise high-radix switches.
  • dual-mode optical switches 515 may comprise multi-ply switches, such as four-ply switches. In various embodiments, dual-mode optical switches 515 may feature integrated silicon photonics that enable them to switch communications with significantly reduced latency in comparison to conventional switching devices. In some embodiments, dual-mode optical switches 515 may constitute leaf switches 530 in a leaf-spine architecture additionally including one or more dual-mode optical spine switches 520 .
  • dual-mode optical switches may be capable of receiving both Ethernet protocol communications carrying Internet Protocol (IP packets) and communications according to a second, high-performance computing (HPC) link-layer protocol (e.g., Intel's Omni-Path Architecture's, Infiniband) via optical signaling media of an optical fabric.
  • HPC high-performance computing
  • connectivity scheme 500 may thus provide support for link-layer connectivity via both Ethernet links and HPC links.
  • both Ethernet and HPC communications can be supported by a single high-bandwidth, low-latency switch fabric.
  • the embodiments are not limited to this example.
  • FIG. 6 illustrates a general overview of a rack architecture 600 that may be representative of an architecture of any particular one of the racks depicted in FIGS. 1 to 4 according to some embodiments.
  • rack architecture 600 may generally feature a plurality of sled spaces into which sleds may be inserted, each of which may be robotically-accessible via a rack access region 601 .
  • rack architecture 600 features five sled spaces 603 - 1 to 603 - 5 .
  • Sled spaces 603 - 1 to 603 - 5 feature respective multi-purpose connector modules (MPCMs) 616 - 1 to 616 - 5 .
  • MPCMs multi-purpose connector modules
  • FIG. 7 illustrates an example of a sled 704 that may be representative of a sled of such a type.
  • sled 704 may comprise a set of physical resources 705 , as well as an MPCM 716 designed to couple with a counterpart MPCM when sled 704 is inserted into a sled space such as any of sled spaces 603 - 1 to 603 - 5 of FIG. 6 .
  • Sled 704 may also feature an expansion connector 717 .
  • Expansion connector 717 may generally comprise a socket, slot, or other type of connection element that is capable of accepting one or more types of expansion modules, such as an expansion sled 718 .
  • expansion connector 717 may provide physical resources 705 with access to supplemental computing resources 705 B residing on expansion sled 718 .
  • the embodiments are not limited in this context.
  • FIG. 8 illustrates an example of a rack architecture 800 that may be representative of a rack architecture that may be implemented in order to provide support for sleds featuring expansion capabilities, such as sled 704 of FIG. 7 .
  • rack architecture 800 includes seven sled spaces 803 - 1 to 803 - 7 , which feature respective MPCMs 816 - 1 to 816 - 7 .
  • Sled spaces 803 - 1 to 803 - 7 include respective primary regions 803 - 1 A to 803 - 7 A and respective expansion regions 803 - 1 B to 803 - 7 B.
  • the primary region may generally constitute a region of the sled space that physically accommodates the inserted sled.
  • the expansion region may generally constitute a region of the sled space that can physically accommodate an expansion module, such as expansion sled 718 of FIG. 7 , in the event that the inserted sled is configured with such a module.
  • FIG. 9 illustrates an example of a rack 902 that may be representative of a rack implemented according to rack architecture 800 of FIG. 8 according to some embodiments.
  • rack 902 features seven sled spaces 903 - 1 to 903 - 7 , which include respective primary regions 903 - 1 A to 903 - 7 A and respective expansion regions 903 - 1 B to 903 - 7 B.
  • temperature control in rack 902 may be implemented using an air cooling system.
  • rack 902 may feature a plurality of fans 919 that are generally arranged to provide air cooling within the various sled spaces 903 - 1 to 903 - 7 .
  • the height of the sled space is greater than the conventional “1 U” server height.
  • fans 919 may generally comprise relatively slow, large diameter cooling fans as compared to fans used in conventional rack configurations. Running larger diameter cooling fans at lower speeds may increase fan lifetime relative to smaller diameter cooling fans running at higher speeds while still providing the same amount of cooling.
  • the sleds are physically shallower than conventional rack dimensions. Further, components are arranged on each sled to reduce thermal shadowing (i.e., not arranged serially in the direction of air flow).
  • the wider, shallower sleds allow for an increase in device performance because the devices can be operated at a higher thermal envelope (e.g., 250 W) due to improved cooling (i.e., no thermal shadowing, more space between devices, more room for larger heat sinks, etc.).
  • a higher thermal envelope e.g. 250 W
  • improved cooling i.e., no thermal shadowing, more space between devices, more room for larger heat sinks, etc.
  • MPCMs 916 - 1 to 916 - 7 may be configured to provide inserted sleds with access to power sourced by respective power modules 920 - 1 to 920 - 7 , each of which may draw power from an external power source 921 .
  • external power source 921 may deliver alternating current (AC) power to rack 902
  • power modules 920 - 1 to 920 - 7 may be configured to convert such AC power to direct current (DC) power to be sourced to inserted sleds.
  • power modules 920 - 1 to 920 - 7 may be configured to convert 277-volt AC power into 12-volt DC power for provision to inserted sleds via respective MPCMs 916 - 1 to 916 - 7 .
  • the embodiments are not limited to this example.
  • MPCMs 916 - 1 to 916 - 7 may also be arranged to provide inserted sleds with optical signaling connectivity to a dual-mode optical switching infrastructure 914 , which may be the same as—or similar to—dual-mode optical switching infrastructure 514 of FIG. 5 .
  • optical connectors contained in MPCMs 916 - 1 to 916 - 7 may be designed to couple with counterpart optical connectors contained in MPCMs of inserted sleds to provide such sleds with optical signaling connectivity to dual-mode optical switching infrastructure 914 via respective lengths of optical cabling 922 - 1 to 922 - 7 .
  • each such length of optical cabling may extend from its corresponding MPCM to an optical interconnect loom 923 that is external to the sled spaces of rack 902 .
  • optical interconnect loom 923 may be arranged to pass through a support post or other type of load-bearing element of rack 902 . The embodiments are not limited in this context. Because inserted sleds connect to an optical switching infrastructure via MPCMs, the resources typically spent in manually configuring the rack cabling to accommodate a newly inserted sled can be saved.
  • FIG. 10 illustrates an example of a sled 1004 that may be representative of a sled designed for use in conjunction with rack 902 of FIG. 9 according to some embodiments.
  • Sled 1004 may feature an MPCM 1016 that comprises an optical connector 1016 A and a power connector 1016 B, and that is designed to couple with a counterpart MPCM of a sled space in conjunction with insertion of MPCM 1016 into that sled space. Coupling MPCM 1016 with such a counterpart MPCM may cause power connector 1016 to couple with a power connector comprised in the counterpart MPCM. This may generally enable physical resources 1005 of sled 1004 to source power from an external source, via power connector 1016 and power transmission media 1024 that conductively couples power connector 1016 to physical resources 1005 .
  • Dual-mode optical network interface circuitry 1026 may generally comprise circuitry that is capable of communicating over optical signaling media according to each of multiple link-layer protocols supported by dual-mode optical switching infrastructure 914 of FIG. 9 .
  • dual-mode optical network interface circuitry 1026 may be capable both of Ethernet protocol communications and of communications according to a second, high-performance protocol.
  • dual-mode optical network interface circuitry 1026 may include one or more optical transceiver modules 1027 , each of which may be capable of transmitting and receiving optical signals over each of one or more optical channels. The embodiments are not limited in this context.
  • Coupling MPCM 1016 with a counterpart MPCM of a sled space in a given rack may cause optical connector 1016 A to couple with an optical connector comprised in the counterpart MPCM.
  • This may generally establish optical connectivity between optical cabling of the sled and dual-mode optical network interface circuitry 1026 , via each of a set of optical channels 1025 .
  • Dual-mode optical network interface circuitry 1026 may communicate with the physical resources 1005 of sled 1004 via electrical signaling media 1028 .
  • a relatively higher thermal envelope e.g. 250 W
  • a sled may include one or more additional features to facilitate air cooling, such as a heatpipe and/or heat sinks arranged to dissipate heat generated by physical resources 1005 .
  • additional features such as a heatpipe and/or heat sinks arranged to dissipate heat generated by physical resources 1005 .
  • any given sled that features the design elements of sled 1004 may also feature an expansion connector according to some embodiments. The embodiments are not limited in this context.
  • FIG. 11 illustrates an example of a data center 1100 that may generally be representative of one in/for which one or more techniques described herein may be implemented according to various embodiments.
  • a physical infrastructure management framework 1150 A may be implemented to facilitate management of a physical infrastructure 1100 A of data center 1100 .
  • one function of physical infrastructure management framework 1150 A may be to manage automated maintenance functions within data center 1100 , such as the use of robotic maintenance equipment to service computing equipment within physical infrastructure 1100 A.
  • physical infrastructure 1100 A may feature an advanced telemetry system that performs telemetry reporting that is sufficiently robust to support remote automated management of physical infrastructure 1100 A.
  • telemetry information provided by such an advanced telemetry system may support features such as failure prediction/prevention capabilities and capacity planning capabilities.
  • physical infrastructure management framework 1150 A may also be configured to manage authentication of physical infrastructure components using hardware attestation techniques. For example, robots may verify the authenticity of components before installation by analyzing information collected from a radio frequency identification (RFID) tag associated with each component to be installed.
  • RFID radio frequency identification
  • the physical infrastructure 1100 A of data center 1100 may comprise an optical fabric 1112 , which may include a dual-mode optical switching infrastructure 1114 .
  • Optical fabric 1112 and dual-mode optical switching infrastructure 1114 may be the same as—or similar to—optical fabric 412 of FIG. 4 and dual-mode optical switching infrastructure 514 of FIG. 5 , respectively, and may provide high-bandwidth, low-latency, multi-protocol connectivity among sleds of data center 1100 .
  • the availability of such connectivity may make it feasible to disaggregate and dynamically pool resources such as accelerators, memory, and storage.
  • one or more pooled accelerator sleds 1130 may be included among the physical infrastructure 1100 A of data center 1100 , each of which may comprise a pool of accelerator resources—such as co-processors and/or FPGAs, for example—that is globally accessible to other sleds via optical fabric 1112 and dual-mode optical switching infrastructure 1114 .
  • accelerator resources such as co-processors and/or FPGAs, for example
  • one or more pooled storage sleds 1132 may be included among the physical infrastructure 1100 A of data center 1100 , each of which may comprise a pool of storage resources that is globally accessible to other sleds via optical fabric 1112 and dual-mode optical switching infrastructure 1114 .
  • such pooled storage sleds 1132 may comprise pools of solid-state storage devices such as solid-state drives (SSDs).
  • SSDs solid-state drives
  • one or more high-performance processing sleds 1134 may be included among the physical infrastructure 1100 A of data center 1100 .
  • high-performance processing sleds 1134 may comprise pools of high-performance processors, as well as cooling features that enhance air cooling to yield a higher thermal envelope of up to 250 W or more.
  • any given high-performance processing sled 1134 may feature an expansion connector 1117 that can accept a far memory expansion sled, such that the far memory that is locally available to that high-performance processing sled 1134 is disaggregated from the processors and near memory comprised on that sled.
  • such a high-performance processing sled 1134 may be configured with far memory using an expansion sled that comprises low-latency SSD storage.
  • the optical infrastructure allows for compute resources on one sled to utilize remote accelerator/FPGA, memory, and/or SSD resources that are disaggregated on a sled located on the same rack or any other rack in the data center.
  • the remote resources can be located one switch jump away or two-switch jumps away in the spine-leaf network architecture described above with reference to FIG. 5 .
  • the embodiments are not limited in this context.
  • one or more layers of abstraction may be applied to the physical resources of physical infrastructure 1100 A in order to define a virtual infrastructure, such as a software-defined infrastructure 1100 B.
  • virtual computing resources 1136 of software-defined infrastructure 1100 B may be allocated to support the provision of cloud services 1140 .
  • particular sets of virtual computing resources 1136 may be grouped for provision to cloud services 1140 in the form of SDI services 1138 .
  • cloud services 1140 may include—without limitation—software as a service (SaaS) services 1142 , platform as a service (PaaS) services 1144 , and infrastructure as a service (IaaS) services 1146 .
  • management of software-defined infrastructure 1100 B may be conducted using a virtual infrastructure management framework 1150 B.
  • virtual infrastructure management framework 1150 B may be designed to implement workload fingerprinting techniques and/or machine-learning techniques in conjunction with managing allocation of virtual computing resources 1136 and/or SDI services 1138 to cloud services 1140 .
  • virtual infrastructure management framework 1150 B may use/consult telemetry data in conjunction with performing such resource allocation.
  • an application/service management framework 1150 C may be implemented in order to provide QoS management capabilities for cloud services 1140 . The embodiments are not limited in this context.
  • an illustrative compute device 1200 for managing a host interface includes a network interface controller (NIC) 1214 having a host interface, designated herein as a “flexible host interface.”
  • NIC network interface controller
  • the flexible host interface is configured to receive messages which trigger various processing events. Such messages require certain protocols for host software and device hardware interactions.
  • the flexible host interface of the illustrative compute device 1200 includes configurable cores of a symmetric multi-processing (SMP) array (see, e.g., the SMP array 1422 of the illustrative flexible host interface 1314 of FIG. 14 ) in the hardware data path, which allows for support of various drivers, models, etc.
  • SMP symmetric multi-processing
  • the flexible host interface receives an indication that a network packet is to be transmitted from the host (i.e., a processor/CPU of the compute device 1200 ) to another compute device or that a network packet has been received by the NIC from another compute device.
  • the host or the NIC depending on the ingress/egress direction of the network packet, will notify the flexible host interface that a network packet is ready to be transferred from the host to the NIC (i.e., the network packet is being transmitted to another compute device via the NIC) or that a network packet is ready to be transferred from the NIC to the host (i.e., the network packet has been received from another compute device at the NIC).
  • the notification is placed in a queue, ring, or some other type of cache storage structure in a memory of the host.
  • a job manager of the flexible host interface retrieves a location of a descriptor associated with the message and transmits a message to the SMP array for processing.
  • the descriptor is associated with a particular portion of a network packet, such as a header, a footer, or at least a portion of the payload, and includes information corresponding thereto.
  • the descriptor typically includes information (i.e., descriptor information) usable to identify a storage location of the associated portion of the network packet.
  • the descriptor information may be used to identify one or more operations to be performed thereon, such as a network protocol associated with a network packet, a type of data associated with the network packet, a packet flow of the network packet, etc. Accordingly, the descriptor information can be used to identify various operations that are to be performed on the portion of the network packet associated with the descriptor, such as direct memory access (DMA) operations, for example.
  • DMA direct memory access
  • the SMP array Upon receipt of the message by the SMP array, the SMP array identifies a core of the SMP array to process the message, which interprets the message to identify a long-latency operation to be performed (e.g., as a function of the descriptor associated with the received message).
  • a long-latency operation may include any type of operation that requires an amount of time to complete that is above a reference threshold, such as a DMA operation.
  • the SMP array Upon identifying the long-latency operation, the SMP array generates a message which includes an indication of the identified long-latency operation, as well as a subsequent operation to be performed upon completion of the long-latency operation.
  • a message intended to perform a DMA operation may include information usable to identify that data is to be fetched, a location of the data to be fetched, and an operation to be performed on the data subsequent to the data having been fetched, as well as other information that may be usable to perform the long-latency operation and/or identify the subsequent operation to be performed.
  • the SMP array Upon completion of the long-latency operation, the SMP array receives a message indicating the requested long-latency operation has been performed, which the SMP array uses to identify what to do upon receipt of the message (e.g., based on the subsequent operation to be performed upon completion of the long-latency operation as indicated by the received message). For example, the SMP array may determine that another long-latency operation is to be performed (i.e., the aforementioned cycle repeats for the other long-latency operation), or that all long-latency operations have been performed such that the network packet associated with the message is ready to be place on the wire (i.e., for transmission to another compute device) or is ready to be forwarded to the host (i.e., the network packet was received from another compute device).
  • another long-latency operation i.e., the aforementioned cycle repeats for the other long-latency operation
  • all long-latency operations have been performed such that the network packet associated with the message is ready to be place on the wire (i.e
  • the compute device 1200 may be embodied as a server (e.g., a stand-alone server, a rack server, a blade server, etc.), a compute node, a storage node, a switch (e.g., a disaggregated switch, a rack-mounted switch, a standalone switch, a fully managed switch, a partially managed switch, a full-duplex switch, and/or a half-duplex communication mode enabled switch), a router, and/or a sled in a data center (e.g., one of the sleds 204 , 404 , 504 , 1004 , 1130 , 1132 , 1134 ), any of which may be embodied as one or more physical and/or virtual devices.
  • a server e.g., a stand-alone server, a rack server, a blade server, etc.
  • a compute node e.g., a storage node
  • a switch e.g.,
  • the illustrative compute device 1200 includes a compute engine 1202 , an input/output (I/O) subsystem 1208 , one or more data storage devices 1210 , communication circuitry 1212 , and, in some embodiments, one or more peripheral devices 1216 .
  • the compute device 1200 may include other or additional components, such as those commonly found in a compute device (e.g., a power supply, cooling component(s), a graphics processing unit (GPU), etc.). It should be appreciated that they types of components may depend on the type and/or intended use of the compute device 1200 .
  • the compute device 1200 may not include the data storage devices.
  • one or more of the illustrative components may be incorporated in, or otherwise form a portion of, another component.
  • the compute engine 1202 may be embodied as any type of device or collection of devices capable of performing various compute functions described below.
  • the compute engine 1202 may be embodied as a single device such as an integrated circuit, an embedded system, an FPGA, a system-on-a-chip (SoC), or other integrated system or device.
  • the compute engine 1202 includes or may otherwise be embodied as a processor 1204 and a memory 1206 .
  • the processor 1204 may be embodied as any type of processor capable of performing the functions described herein.
  • the processor 1204 may be embodied as one or more single or multi-core processors, a microcontroller, or other processor or processing/controlling circuit.
  • the processor 1204 may be embodied as, include, or otherwise be coupled to an FPGA, an application specific integrated circuit (ASIC), reconfigurable hardware or hardware circuitry, or other specialized hardware to facilitate performance of the functions described herein.
  • ASIC application specific integrated circuit
  • the memory 1206 may be embodied as any type of volatile (e.g., dynamic random access memory (DRAM), etc.) or non-volatile memory or data storage capable of performing the functions described herein. It should be appreciated that the memory 1206 may include main memory (i.e., a primary memory) and/or cache memory (i.e., memory that can be accessed more quickly than the main memory). Volatile memory may be a storage medium that requires power to maintain the state of data stored by the medium. Non-limiting examples of volatile memory may include various types of random access memory (RAM), such as dynamic random access memory (DRAM) or static random access memory (SRAM).
  • RAM random access memory
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • DRAM synchronous dynamic random access memory
  • DRAM of a memory component may comply with a standard promulgated by JEDEC, such as JESD79F for DDR SDRAM, JESD79-2F for DDR2 SDRAM, JESD79-3F for DDR3 SDRAM, JESD79-4A for DDR4 SDRAM, JESD209 for Low Power DDR (LPDDR), JESD209-2 for LPDDR2, JESD209-3 for LPDDR3, and JESD209-4 for LPDDR4 (these standards are available at www.jedec.org).
  • LPDDR Low Power DDR
  • Such standards may be referred to as DDR-based standards and communication interfaces of the storage devices that implement such standards may be referred to as DDR-based interfaces.
  • the memory device is a block addressable memory device, such as those based on NAND or NOR technologies.
  • a memory device may also include future generation nonvolatile devices, such as a three dimensional crosspoint memory device (e.g., Intel 3D XPointTM memory), or other byte addressable write-in-place nonvolatile memory devices.
  • the memory device may be or may include memory devices that use chalcogenide glass, multi-threshold level NAND flash memory, NOR flash memory, single or multi-level Phase Change Memory (PCM), a resistive memory, nanowire memory, ferroelectric transistor random access memory (FeTRAM), anti-ferroelectric memory, magnetoresistive random access memory (MRAM) memory that incorporates memristor technology, resistive memory including the metal oxide base, the oxygen vacancy base and the conductive bridge Random Access Memory (CB-RAM), or spin transfer torque (STT)-MRAM, a spintronic magnetic junction memory based device, a magnetic tunneling junction (MTJ) based device, a DW (Domain Wall) and SOT (Spin Orbit Transfer) based device, a thyristor based memory device, or a combination of any of the above, or other memory.
  • the memory device may refer to the die itself and/or to a packaged memory product.
  • 3D crosspoint memory may comprise a transistor-less stackable cross point architecture in which memory cells sit at the intersection of word lines and bit lines and are individually addressable and in which bit storage is based on a change in bulk resistance.
  • all or a portion of the memory 1206 may be integrated into the processor 1204 .
  • the memory 1206 may store various software and data used during operation such as job request data, kernel map data, telemetry data, applications, programs, libraries, and drivers.
  • the compute engine 1202 is communicatively coupled to other components of the compute device 1200 via the I/O subsystem 1208 , which may be embodied as circuitry and/or components to facilitate input/output operations with the compute engine 1202 (e.g., with the processor 1204 and/or the memory 1206 ) and other components of the compute device 1200 .
  • the I/O subsystem 1208 may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, integrated sensor hubs, firmware devices, communication links (e.g., point-to-point links, bus links, wires, cables, light guides, printed circuit board traces, etc.), and/or other components and subsystems to facilitate the input/output operations.
  • the I/O subsystem 1208 may form a portion of a SoC and be incorporated, along with one or more of the processor 1204 , the memory 1206 , and other components of the compute device 1200 , into the compute engine 1202 .
  • the compute device 1200 may include one or more data storage devices 1210 , which may be embodied as any type of devices configured for short-term or long-term storage of data such as, for example, memory devices and circuits, memory cards, hard disk drives, solid-state drives, or other data storage devices.
  • Each data storage device 1210 may include a system partition that stores data and firmware code for the data storage device 1210 . Additionally, each data storage device 1210 may also include an operating system partition that stores data files and executables for an operating system.
  • the communication circuitry 1212 may be embodied as any communication circuit, device, or collection thereof, capable of enabling network communications between the compute device 1200 and another compute device (e.g., a source compute device) over a network (not shown).
  • a network may be embodied as any type of wired or wireless communication network, including global networks (e.g., the Internet), local area networks (LANs) or wide area networks (WANs), cellular networks (e.g., Global System for Mobile Communications (GSM), 3G, Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), etc.), digital subscriber line (DSL) networks, cable networks (e.g., coaxial networks, fiber networks, etc.), or any combination thereof.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • WiMAX Worldwide Interoperability for Microwave Access
  • DSL digital subscriber line
  • cable networks e.g., coaxial networks, fiber networks, etc.
  • the communication circuitry 1212 may be configured to use any one or more communication technology (e.g., wired or wireless communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication.
  • the illustrative communication circuitry 1212 includes the NIC 1214 , which may also be referred to as a smart NIC or an intelligent/smart host fabric interface (HFI), and is described in further detail in FIGS. 13 and 14 .
  • the NIC 1214 may be embodied as one or more add-in-boards, daughter cards, network interface cards, controller chips, chipsets, or other devices that may be used by the compute device 1200 to transmit/receive network communications to/from another compute device.
  • the peripheral device(s) 1216 may include any type of device that is usable to input information into the compute device 1200 and/or receive information from the compute device 1200 .
  • the peripheral devices 1216 may be embodied as any auxiliary device usable to input information into the compute device 1200 , such as a keyboard, a mouse, a microphone, a barcode reader, an image scanner, etc., or output information from the compute device 1200 , such as a display, a speaker, graphics circuitry, a printer, a projector, etc. It should be appreciated that, in some embodiments, one or more of the peripheral devices 1216 may function as both an input device and an output device (e.g., a touchscreen display, a digitizer on top of a display screen, etc.).
  • an output device e.g., a touchscreen display, a digitizer on top of a display screen, etc.
  • peripheral devices 1216 connected to the compute device 1200 may depend on, for example, the type and/or intended use of the compute device 1200 . Additionally or alternatively, in some embodiments, the peripheral devices 1216 may include one or more ports, such as a USB port, for example, for connecting external peripheral devices to the compute device 1200 .
  • the NIC 1214 of the compute device 1200 of FIG. 12 may establish an environment 1300 during operation.
  • the illustrative environment 1300 includes a network interface 1302 , a memory fabric 1306 of a memory fabric 1306 , a flexible packet processor (FXP) 1308 , one or more accelerator agents 1310 , a traffic manager 1312 , the flexible host interface 1314 , an infrastructure 1316 , one or more on-die processing cores 1318 , a memory steering unit 1320 , an SRAM 1322 , and one or more memory controllers 1324 communicatively coupled to DDR SDRAM 1326 .
  • the various components of the environment 1300 may be embodied as hardware, firmware, software, or a combination thereof.
  • one or more of the components of the environment 1300 may be embodied as circuitry or collection of electrical devices. Additionally, in some embodiments, one or more of the illustrative components may form a portion of another component and/or one or more of the illustrative components may be independent of one another.
  • the network interface 1302 is configured to receive inbound network traffic and route/transmit outbound network traffic. To facilitate the receipt of inbound and transmission of outbound network communications (e.g., network traffic, network packets, network packet flows, etc.) to/from the compute device 1200 , the network interface 1302 is configured to manage (e.g., create, modify, delete, etc.) connections to physical and virtual network ports (i.e., virtual network interfaces) of the NIC 1214 , as well as the ingress/egress buffers/queues associated therewith. The network interface 1302 is additionally configured to coordinate with the memory fabric interface 1304 to store the contents (e.g., header(s), payload, footer(s), etc.) of network packets received at the network interface 1302 to the memory fabric 1306 .
  • the memory fabric interface 1304 to store the contents (e.g., header(s), payload, footer(s), etc.) of network packets received at the network interface 1302 to the memory fabric 1306 .
  • the memory fabric 1306 includes multiple memory storage components (not shown) referred to herein as segments, each of which are usable to support the distributed storage of the contents of a network packet. Accordingly, it should be appreciated that the memory fabric interface 1304 is configured to manage the data writes to the segments in a distributed fashion and provide an indication (e.g., a pointer) usable to identify the storage locations of the segments in which the contents of each network packet has been stored. Additionally, the memory fabric interface 1304 is configured to notify the FXP 1308 when a network packet has been stored in the memory fabric 1306 and provide the memory fabric location pointer(s) to the FXP 1308 .
  • an indication e.g., a pointer
  • the one or more accelerator agents 1310 are configured to perform an acceleration operation on at least a portion of a network packet.
  • the accelerator agents 1310 may include a remote direct memory access (RDMA) operation, a cryptography operation, or any other type of acceleration.
  • the traffic manager 1312 is configured to perform traffic-management in the packet-processing data path, such as may be performed to enforce service-level agreements (SLAs). As will be described in additional detail below, the traffic manager 1312 is configured to throttle the transmission of network packets from the host CPU(s) to the wire.
  • SLAs service-level agreements
  • the one or more on-die cores 1318 are configured to perform computations local to the NIC 1214 . Accordingly, the on-die cores 1318 can provide computational power to perform certain operations without the data being operated on having to be moved to a location remote of the NIC 1214 , thereby eliminating the latency otherwise introduced by moving the data.
  • the infrastructure 1316 may include various components to manage the communications, state, and controls of the on-die cores 1318 and/or the host interface 1314 , such as a serial communication interface (e.g., a universal asynchronous receiver and transmitter (UART), a serial peripheral interface (SPI) bus, etc.), a testing/debugging interface, a digital thermal sensor, I/O controllers, etc.
  • a serial communication interface e.g., a universal asynchronous receiver and transmitter (UART), a serial peripheral interface (SPI) bus, etc.
  • SPI serial peripheral interface
  • testing/debugging interface e.g., a digital thermal sensor, I/O controllers,
  • the SRAM 1322 is communicatively coupled to the on-die cores 1318 via a memory steering unit 1320 and may be used to store data (e.g., work queues, notifications, interrupts, headers, descriptors, critical structures, etc.) for the on-die cores 1318 .
  • the memory steering unit 1320 is also coupled to one or more memory controllers 1324 .
  • the memory controllers 1324 may be double data rate (DDR) memory controllers configured to drive the DDR SDRAM 1326 external to, but managed by the NIC 1214 , rather than the host CPUs (e.g., the processor(s) 1204 of the compute engine 1202 of FIG. 12 ).
  • DDR double data rate
  • the memory controllers 1324 are additionally communicatively coupled to the memory fabric 1306 via the memory fabric interface 1304 , such that data stored in the DDR SDRAM 1326 can be transferred to/from the memory fabric 1306 .
  • the flexible host interface 1314 may be embodied as any type of host interface device capable of performing the functions described herein.
  • the flexible host interface 1314 is configured to function as an interface between each of the host CPUs 1328 (e.g., each of the processors 1204 of the compute engine 1202 of FIG. 12 ) and the NIC 1214 .
  • the flexible host interface 1314 is configured to function as an interface between the host CPUs 1328 (e.g., one of the processors 1204 of the compute engine 1202 of FIG. 12 ) and the memory fabric 1306 (e.g., via the memory fabric interface 1304 ), as well as function as an interface between the host CPUs 1328 and the infrastructure 1316 .
  • messages and/or network packet data may be passed therebetween via one or more communication links, such as PCIe interconnects, to provide access to the host memory 1330 (e.g., the memory 1206 of the compute engine 1202 of FIG. 12 ).
  • the flexible host interface 1314 of the NIC 1214 of FIGS. 12 and 13 may establish an environment 1400 during operation.
  • the illustrative environment 1400 includes an event logic unit manager 1402 , a messaging queue manager 1412 , an SMP array 1422 , a DMA queue manager 1430 , a DMA engine 1434 , a descriptor queue manager 1440 , a job manager 1444 , an offload queue manager 1448 , and an offload/park manager 1452 .
  • the various components of the environment 1400 may be embodied as physical and/or virtual hardware, firmware, software, or a combination thereof.
  • one or more of the components of the environment 1400 may be embodied as circuitry or collection of electrical devices. Additionally, in some embodiments, one or more of the illustrative components may form a portion of another component and/or one or more of the illustrative components may be independent of one another.
  • the event logic unit manager 1402 includes multiple event logic units 1404 , each of which are configured to receive (e.g., via a PCIe connection) inbound event notifications received at the flexible host interface 1314 .
  • the illustrative event logic unit manager 1402 includes a fabric event logic unit 1406 , a memory-mapped I/O (MMIO) event logic unit 1408 , and a signaling event logic unit 1410 .
  • MMIO memory-mapped I/O
  • the event logic units 1404 of the event logic unit manager 1402 are not limited to those of the illustrative event logic unit manager 1402 . In other words, in other embodiments, the event logic unit manager 1402 may be configured to manage additional and/or alternative event logic units 1404 .
  • Each of the event logic units 1404 are configured to receive a particular type, or set of types, of event messages, as well as interpret and queue messages corresponding to the received messaged. Additionally, each of the event logic units 1404 are configured to build data structures based on an associated protocol which is readable by the SMP array 1422 .
  • the fabric event logic unit 1406 may be configured to receive and interpret host fabric interface events, such as a message indicating a network packet is to be transmitted between the NIC 1214 and one of the host CPUs 1328 .
  • the MMIO event logic unit 1408 may be configured to receive and interpret an indication from a host software application that data, a notification, or a message is available.
  • the signaling event logic unit 1410 may be configured to receive and interpret fixed function signal requests (e.g., interrupts) between the NIC 1214 and the host CPUs 1328 .
  • the messaging queue manager 1412 is configured to manage event message queues 1414 between the event logic units 1404 and the SMP array 1422 . To do so, the messaging queue manager 1412 is configured to create/destroy the appropriate event message queues 1414 based on the corresponding event logic units 1404 . In some embodiments, the messaging queue manager 1412 is additionally configured to enqueue and dequeue messages into/from the appropriate one of the event message queues 1414 .
  • the illustrative messaging queue manager 1412 includes one or more fabric event queues 1416 (i.e., for queueing messages received from the fabric event logic unit 1406 ), one or more MMIO event queues 1418 (i.e., for queueing messages receive from the MMIO event logic unit 1408 ), and one or more signaling event queues 1420 (i.e., for queueing messages receive from the signaling event logic unit 1410 ).
  • fabric event queues 1416 i.e., for queueing messages received from the fabric event logic unit 1406
  • MMIO event queues 1418 i.e., for queueing messages receive from the MMIO event logic unit 1408
  • signaling event queues 1420 i.e., for queueing messages receive from the signaling event logic unit 1410 .
  • the SMP array 1422 which is described in further detail throughout, is configured to process queued messages of various types having various formats (e.g., via pipeline structured logic). To do so, the illustrative SMP array 1422 includes a pool of processor cores 1424 , an arbitrator 1426 , and a scheduler 1428 . While the pool of processor cores 1424 illustratively shows 16 cores, it should be appreciated the pool of processor cores 1424 may include any number of multiple cores (e.g., 4 cores, 8 cores, 32 cores, etc.) depending on the embodiment.
  • processor cores 1424 which may depend on the intended use of the NIC 1214 (e.g., model), or the processor cores 1424 themselves (e.g., a certain number of cores dedicated to processing a particular message type while a certain number of other cores are dedicated to processing another message type, etc.).
  • Each of the processor cores 1424 may be embodied as any type of processor core capable of performing the functions described herein, such as general purpose cores, application-specific instruction set processors, and/or the like.
  • the arbitrator 1426 is configured to manage arbitration between messages to be processed by the SMP array 1422
  • the scheduler 1428 is configured to schedule the messages for processing by the SMP array 1422 , such as to a particular one of the processor cores 1424 .
  • the DMA queue manager 1430 is configured to manage one or more DMA queues 1432 . To do so, the DMA queue manager 1430 is configured to create/destroy the DMA queues 1432 , as may be required from time to time. In some embodiments, the DMA queue manager 1430 is additionally configured to queue/dequeue messages received from the SMP array 1422 for receipt by the DMA engine 1434 and/or queue/dequeue messages received from the DMA engine 1434 for receipt by the SMP array 1422 .
  • the DMA engine 1434 is configured to facilitate DMA operations to be performed. Accordingly, the DMA engine 1434 can access host memory (e.g., the host memory 1330 of FIG. 13 ) independent of the host CPU (e.g. one of the host CPUs 1328 of FIG. 13 ). To do so, the illustrative DMA engine 1434 includes one or more DMA cores 1436 and a DMA controller 1438 .
  • the DMA cores 1436 are configured to interpret messages from the DMA queues 1432 and perform the DMA fetch operations associated therewith.
  • the DMA controller 1438 is configured to schedule/pre-fetch the messages from the DMA queues 1432 .
  • the DMA controller 1438 may be additionally configured to manage the scheduling of messages received from other components of the flexible host interface 1314 , such as the event logic unit manager 1402 , the messaging queue manager 1412 , and the job manager 1444 , for example.
  • the descriptor queue manager 1440 is configured to manage one or more descriptor queues 1442 . To do so, the descriptor queue manager 1440 is configured to create/destroy the descriptor queues 1442 , as may be required from time to time. In some embodiments, the descriptor queue manager 1440 is additionally configured to queue/dequeue messages received from the SMP array 1422 for receipt by the job manager 1444 and/or queue/dequeue messages received from the job manager 1444 for receipt by the SMP array 1422 .
  • the job manager 1444 is configured to manage the distribution of descriptors received for processing.
  • the illustrative job manager includes multiple processor cores 1442 .
  • Each of the processor cores 1442 may be embodied as any type of processor core capable of performing the functions described herein, such as general purpose cores, application-specific instruction set processors, and/or the like.
  • the job manager 1444 may be configured to regulate which descriptors are processed by which processor cores 1442 . For example, in some embodiments, the job manager 1444 may identify a flow associated with the descriptor and determine which of the processor cores 1442 should process the descriptor as a function of the flow. Alternatively, in other embodiments, the job manager 1444 may be configured to process a descriptor as a function of which of the processor cores 1442 is available.
  • the job manager 1444 may be configured to communicate with a traffic manager of the NIC 1214 (e.g., the traffic manager 1312 of the illustrative NIC 1214 of FIG. 13 ). In other words, in such embodiments, the job manager 1444 may be configured to only process descriptors based on certain conditions as set forth by the traffic manager 1312 . For example, the job manager 1444 may be configured to receive an authorized traffic limit from the traffic manager 1312 , which indicates a size (e.g., a number of bits, a total number, etc.) of network packets which the job manager 1444 is allowed to queue (i.e., in one of the descriptor queues 1442 ). Accordingly, the job manager 1444 effectively throttles the amount of traffic that is being processed by the SMP array 1422 and transmitted from the NIC 1214 .
  • a traffic manager of the NIC 1214 e.g., the traffic manager 1312 of the illustrative NIC 1214 of FIG. 13 .
  • the offload queue manager 1448 is configured to manage one or more offload queues 1450 . To do so, the offload queue manager 1448 is configured to create/destroy the offload queues 1450 , as may be required from time to time. In some embodiments, the offload queue manager 1448 is additionally configured to queue/dequeue messages received from the SMP array 1422 for receipt by the offload/park manager 1452 and/or queue/dequeue messages received from the offload/park manager 1452 for receipt by the SMP array 1422 .
  • the offload/park manager 1452 is configured to manage offload and park operations to be performed on at least a portion of a network packet (e.g., a header, a footer, a payload, or a portion thereof).
  • a network packet e.g., a header, a footer, a payload, or a portion thereof.
  • the offload/park manager 1452 may be configured to manage checksum validations, tag extractions, segmentation, etc.
  • the compute device 1200 may execute a method 1500 for generating one or more descriptors for a network packet.
  • the method 1500 begins in block 1502 , in which the host CPU 1328 determines whether a network packet has been built for transmission to another compute device. If so, the method 1500 advances to block 1504 , in which the host CPU 1328 generates one or more appropriate descriptors for the network packet. It should be appreciated that more than one descriptor may correspond to a given network packet.
  • descriptors are associated with a network packet, or a particular portion thereof. Accordingly, for example, one descriptor may correspond to a payload of the network packet, while another descriptor may correspond to a header of the network packet.
  • the descriptor additionally includes information (i.e., descriptor information) usable to identify a storage location of the associated portion of the network packet, as well as a network protocol associated with a network packet.
  • the descriptor may include additional information which indicates or is otherwise usable to identify a type of data associated with the network packet, a packet flow of the network packet, etc. Accordingly, the descriptor information may be used to identify one or more operations to be performed thereon.
  • the host CPU 1328 stores the generated descriptor(s) into an array of descriptors.
  • the array of descriptors may be structured as a descriptor table stored in a cache memory accessible by the host CPU 1328 . It should be appreciated that, in other embodiments, the descriptor(s) may be placed into an alternative cache data structure.
  • the host CPU 1328 identifies the array index corresponding to each location of the stored descriptor(s).
  • the host CPU 1328 places the identified index(es) into a descriptor ring, which may be stored in a cache memory accessible by the host CPU 1328 .
  • the host CPU 1328 transmits a notification (i.e., a descriptor notification) to a flexible host interface (e.g., the illustrative flexible host interface 1314 of FIG. 14 ) of the NIC 1214 which notifies the NIC 1214 that the one or more generated descriptors have been placed into to the array of descriptors and the corresponding index(s) in the descriptor ring.
  • a notification i.e., a descriptor notification
  • a flexible host interface e.g., the illustrative flexible host interface 1314 of FIG. 14
  • the host CPU 1328 may include in the notification an indication of the number of indices placed into the descriptor ring.
  • the compute device 1200 may execute a method 1600 for notifying a traffic manager of the NIC (e.g., the traffic manager 1312 of the NIC 1214 of FIG. 13 ) of the receipt of one or more descriptors from a host CPU of the compute device 1200 (e.g., one of the host CPUs 1328 of FIG. 13 ).
  • the method 1600 begins in block 1602 , in which the flexible host interface 1314 determines whether a descriptor notification has been received (e.g., as generated in block 1508 of the method 1500 of FIG. 5 ). If so, the method 1600 advances to block 1604 , in which the flexible host interface 1314 identifies a number of descriptors placed into the descriptor ring.
  • the flexible host interface 1314 transmits a notification to a traffic manager indicating the receipt of the descriptor notification which is usable by the traffic manager to manage whether descriptors are presently available for processing in the descriptor ring.
  • the flexible host interface 1314 may include an indication of the number of descriptors placed into the descriptor ring. It should be appreciated that, in some embodiments, the traffic manager 1312 does not regulate the transmission traffic. Accordingly, in such embodiments, the method 1600 may not be performed.
  • the compute device 1200 may execute a method 1700 for processing messages received at the SMP array.
  • the method 1700 begins in block 1702 , in which the SMP array 1422 determines whether to retrieve a message in a message queue (e.g., one of the event message queues 1414 , the DMA queues 1432 , the descriptor queues 1442 , the offload queues 1450 , etc.).
  • a message queue e.g., one of the event message queues 1414 , the DMA queues 1432 , the descriptor queues 1442 , the offload queues 1450 , etc.
  • the queued messages may be formatted based on various different protocols.
  • the event logic units 1404 are configured to build messages having data structures based on an associated protocol which is readable by the SMP array 1422 . Accordingly, it should be appreciated that the SMP array 1422 can dynamically support processing of multiple protocols, such as may be based on assignment at initialization (e.g., of a virtual function which has been mapped to a particular message queue).
  • the method 1700 advances to block 1704 , in which the SMP array 1422 retrieves the message from the appropriate message queue.
  • the SMP array 1422 identifies a core (e.g., one of the processor cores 1424 of FIG. 14 ) to process the retrieved message.
  • the SMP array 1422 or more particularly the identified core of the SMP array 1422 , processes the retrieved message to identify whether any long-latency operations (e.g., a DMA fetch operation) need to be performed.
  • the SMP array 1422 determines whether any long-latency operations were identified.
  • the method 1700 branches to block 1712 , in which the SMP array 1422 identifies instructions to be performed as a function of the identified long-latency operation. For example, if the long-latency operation has been identified as a DMA operation, the instructions may include a fetch instruction with any information necessary to perform the DMA fetch operation.
  • the SMP array 1422 generates a message which includes the identified instructions.
  • the SMP array 1422 includes the next step to be performed into the message (e.g., an operation to be performed subsequent to the long-latency operation having completed).
  • the SMP array 1422 transmits the generated message to an appropriate hardware unit scheduler (e.g., the DMA controller 1438 of the illustrative DMA engine 1434 of FIG. 14 ) to perform the long-latency operation.
  • an appropriate hardware unit scheduler e.g., the DMA controller 1438 of the illustrative DMA engine 1434 of FIG. 14
  • the method 1700 branches to block 1720 .
  • the SMP array 1422 generates a message (i.e., a release message) which indicates the network packet associated with the received message can be released to the host (e.g., the network packet was received by the NIC 1214 ) or the NIC 1214 (e.g., the network packet is being transmitted from the NIC 1214 ).
  • the SMP array 1422 transmits the message to a memory fabric interface of a memory fabric (e.g., the memory fabric interface 1304 of the memory fabric 1306 ) of the NIC 1214 to release the network packet.
  • an embodiment of a communication flow 1800 for processing network packets at the flexible host interface 1314 includes the job manager 1444 , the SMP array 1422 , and the DMA engine 1434 of the illustrative flexible host interface 1314 of FIG. 14 .
  • the illustrative communication flow 1800 includes a number of data flows, some of which may be executed separately or together, depending on the embodiment.
  • the job manager 1444 retrieves an index of a descriptor from a descriptor ring, which corresponds to the index of the descriptor in an array of descriptors (e.g., stored in a data table in cache memory accessible by the host CPU 1328 ).
  • the index of the descriptor was placed in the descriptor ring by a host CPUs of the compute device 1200 (e.g., one of the host CPUs 1328 of FIG. 13 ), an example of which is described in the method 1500 of FIG. 15 above.
  • the job manager 1444 may have to receive permission from a traffic manager of the NIC 1214 (e.g., the traffic manager 1312 of the illustrative NIC 1214 of FIG. 13 ), which is described below in the method 1900 of FIG. 19 .
  • descriptors are associated with at least a portion of a network packet (e.g., the entire network packet, a header of the network packet, a footer of the network packet, or at least a portion of a payload of the network packet).
  • the descriptor additionally includes descriptor information which is usable to identify a storage location of the associated portion of the network packet, as well as a network protocol associated with a network packet and/or additional information which indicates or is otherwise usable to identify a type of data associated with the network packet, a packet flow of the network packet, etc., such that the descriptor information may be used to identify one or more operations to be performed on the corresponding portion of the network packet.
  • the job manager 1444 In data flow 1804 , the job manager 1444 generates a message that includes the retrieved index of the descriptor. In data flow 1806 , the job manager 1444 forwards the message to the SMP array 1422 . While not illustratively shown, it should be appreciated that the message is queued in a descriptor queue (e.g., one of the descriptor queues 1442 managed by the descriptor queue manager 1440 ), which can be retrieved by the SMP array 1422 . In data flow 1808 , the scheduler 1428 of the SMP array 1422 identifies which processor core of a pool of processor cores 1424 of the SMP array 1422 is to process the message.
  • a descriptor queue e.g., one of the descriptor queues 1442 managed by the descriptor queue manager 1440
  • the scheduler 1428 of the SMP array 1422 identifies which processor core of a pool of processor cores 1424 of the SMP array 1422 is to process the message.
  • the processor cores 1424 may be treated as one pool of processors, each usable on a first available basis to process a message. Alternatively, as also described previously, the processor cores 1424 may be partitioned into groups such that each group is configured to process a particular type, or set of types, of messages.
  • the scheduler 1428 notifies the identified core of the arrival of the message to be processed.
  • the identified one of the processor cores 1424 processes the message to identify the location of the descriptor based on the index of the descriptor included in the message.
  • the identified processor core 1424 generates another message which indicates to fetch and process the descriptor. It should be appreciated that the fetch operation is an identified long-latency operation and the descriptor processing operation is to be performed by the SMP array 1422 , or more particularly be one of the processor cores 1424 of the SMP array 1422 , upon completion of the identified long-latency operation (i.e., the fetch operation).
  • the identified processor core 1424 forwards the message to the DMA engine 1434 to perform the fetch operation. While not illustratively shown, it should be appreciated that the message is queued in a DMA queue (e.g., one of the DMA queues 1432 managed by the DMA queue manager 1430 ), which can be retrieved by the DMA engine 1434 . In data flow 1818 , the identified processor core 1424 halts and becomes available to process another message.
  • a DMA queue e.g., one of the DMA queues 1432 managed by the DMA queue manager 1430
  • the DMA engine 1434 upon processing of the message receive in data flow 1816 and determining a descriptor fetch operation is being requested (e.g., such as may be determined by a DMA core 1436 of the illustrative DMA engine 1434 of FIG. 14 as directed by the DMA controller 1438 of the DMA engine 1434 ), fetches the descriptor from the host (e.g., from a table of descriptors stored by one of the host CPUs 1328 ) based on the index of the descriptor included in the message.
  • a descriptor fetch operation e.g., such as may be determined by a DMA core 1436 of the illustrative DMA engine 1434 of FIG. 14 as directed by the DMA controller 1438 of the DMA engine 1434 ) fetches the descriptor from the host (e.g., from a table of descriptors stored by one of the host CPUs 1328 ) based on the index of the descriptor included in the message.
  • the DMA engine 1434 In data flow 1822 , in response to the fetch operation having completed (i.e., the descriptor having been fetched and stored in a memory buffer accessible by the SMP array 1422 ), the DMA engine 1434 generates a message which includes the descriptor and indicates to process the descriptor. In data flow 1824 , the DMA engine 1434 forwards the message to the SMP array 1422 . As described previously, such messages are queued in a DMA queue (e.g., one of the DMA queues 1432 managed by the DMA queue manager 1430 ), which can be retrieved by the SMP array 1422 .
  • a DMA queue e.g., one of the DMA queues 1432 managed by the DMA queue manager 1430
  • the scheduler 1428 of the SMP array 1422 identifies which process core of the pool of processor cores 1424 is to process the message.
  • the scheduler 1428 notifies the identified processor core 1424 of the received message to be processed.
  • the identified processor core 1424 processes the message to identify a buffer host address of a network packet.
  • the descriptor may alternatively correspond to a portion of the network packet (e.g., a header, a footer, a portion of payload, etc.).
  • the identified processor core 1424 In data flow 1832 , the identified processor core 1424 generates a message indicating a payload of the network packet is to be fetched at the packet buffer host address in host memory (e.g., the memory 1206 of the compute engine 1202 of FIG. 12 ). Additionally, the identified processor core 1424 includes an indication in the message that indicates the operation to be performed subsequent to the fetch having completed is to transmit the fetched payload (e.g., on the wire to another compute device). In other words, there are no more long-latency operations to be performed on the network packet.
  • the identified processor core 1424 forwards the message to the DMA engine 1434 to perform the fetch operation. While not illustratively shown, as noted previously, it should be appreciated that the message is queued in one of the DMA queues 1432 , which allows for the message to be retrieved by the DMA engine 1434 at its discretion. In data flow 1836 , the identified processor core 1424 halts and becomes available to process another message.
  • the DMA engine 1434 fetches the payload of the network packet from the packet buffer host address (i.e., in host memory).
  • the DMA engine 1434 upon the fetch operation having completed (i.e., the payload has been fetched from host memory and stored in a temporary buffer, such as the SRAM 1322 or the DDR SDRAM 1326 ), the DMA engine 1434 generates a message which indicates the payload is available for transmission and to transmit the associated network packet.
  • the DMA engine 1432 forwards the message to the SMP array 1422 .
  • the message is queued in one of the descriptor queues 1442 , which allows for the message to be retrieved by the SMP array 1422 at its discretion.
  • the scheduler 1428 of the SMP array 1422 identifies which process core of the pool of processor cores 1424 is to process the message.
  • the scheduler 1428 notifies the identified processor core 1424 of the received message to be processed.
  • the identified processor core 1424 processes the message to identify whether another long-latency operation has been request or whether the network packet can be released. It should be appreciated that for the purposes of this illustrative example, the message generated in data flow 1840 indicated that the network packet is to be transmitted.
  • the identified processor core 1424 transmits an indication to a memory fabric interface (e.g., the memory fabric interface 1304 of the memory fabric 1306 ) indicating that the network packet can be released to the memory fabric for transmission therefrom to another compute device.
  • a memory fabric interface e.g., the memory fabric interface 1304 of the memory fabric 1306
  • a similar set of data flows may be performed of a communication flow for processing a network packet in response to having received the network packet at the NIC 1214 from another compute device, culminating in the network packet being released from the memory fabric to an applicable host memory after the appropriate long-latency operations have been identified and performed.
  • the job manager 1444 may be configured to initiate the processing of outbound network packets based on certain criteria, such as whether a processor core of the job manager 1444 (e.g., one of the processor cores 1446 of the illustrative job manager 1444 of FIG. 14 ) is available, a number of messages presently enqueuer in a descriptor queue (e.g., one of the descriptor queues 1442 of FIG. 14 ) relative to a capacity of the descriptor queue (i.e., a fullness level), etc.
  • the job manager 1444 may only allow one descriptor from a given queue to be in-flight at any point in time (i.e., a single-queue line rate).
  • the job manager 1444 may rely on the traffic manager 1312 to dictate how many network packets are to be in process for transit at a given point in time.
  • the compute device 1200 may execute a method 1900 for throttling the processing of outbound network packets.
  • the method 1900 begins in block 1902 , in which the job manager 1444 determines whether a transmit packet grant message has been received from a traffic manager of the NIC 1214 (e.g., the traffic manager 1312 of FIG. 13 ).
  • the method 1900 advances to block 1904 , in which the job manager 1444 identifies a limit on an amount of network traffic authorized by the traffic manager 1312 for transmission from the NIC 1214 (i.e., an authorized traffic limit).
  • a limit on an amount of network traffic authorized by the traffic manager 1312 for transmission from the NIC 1214 i.e., an authorized traffic limit.
  • the other transmit traffic restrictions may include a restriction that only a certain network packet type, priority, or flow is to be processed at a given point in time.
  • the job manager 1444 retrieves a descriptor from a descriptor cache (e.g., via a DMA request to the DMA engine 1434 ).
  • the job manager 1444 interprets the received descriptor.
  • the job manager 1444 determines an amount of network traffic associated with the descriptor.
  • the amount of network traffic may be any value usable to identify the size of the network traffic to be processed that is associated with the descriptor, such as a size relative to an entire network packet (e.g., one half of a network packet, an entire network packet, a header, etc.), a number of bits, etc.
  • the job manager 1444 compares the authorized traffic limit against the determined amount of network traffic associated with the descriptor. In block 1914 , the job manager 1444 determines whether the authorized traffic limit would be exceeded as a function of the comparison performed in block 1912 . If so, the method 1900 branches to block 1916 , in which the job manager 1444 returns the descriptor to the descriptor cache; otherwise, the method branches to block 1918 . In block 1918 , the job manager 1444 decreases the authorized traffic limit by the amount of network traffic associated with the descriptor. In block 1920 , the job manager 1444 generates a message that includes information usable to locate the descriptor, such as an index of the descriptor in the descriptor cache, a temporary buffer location of the descriptor, etc.
  • the job manager 1444 inserts the message into a descriptor queue (e.g., one of the descriptor queues 1442 of FIG. 14 ).
  • the job manager 1444 determines whether the authorized traffic limit has been reached (i.e., whether the decreased the authorized traffic limit is zero or below a particular minimum threshold). If so, the method 1900 returns to block 1902 to determine whether another transmit packet grant message has been received; otherwise, the method 1900 returns to block 1906 to retrieve another descriptor from a description cache.
  • An embodiment of the technologies disclosed herein may include any one or more, and any combination of, the examples described below.
  • Example 1 includes a compute device for processing network packets, the compute device comprising a compute engine having one or more processors and a memory; and a network interface controller (NIC) having a host interface, wherein the NIC is to retrieve, by a symmetric multi-purpose (SMP) array of the host interface, a message from a message queue of the host interface; process, by a processor core of a plurality of processor cores of the SMP array, the message to identify a long-latency operation to be performed on at least a portion of a network packet associated with the message; generate, by the processor core and in response to having identified the long-latency operation to be performed, another message which includes an indication of the long-latency operation to be performed and a next step to be performed upon completion of the long-latency operation; and transmit, by the processor core, the other message to a corresponding hardware unit scheduler of the host interface as a function of the long-latency operation to be performed.
  • SMP symmetric multi-purpose
  • Example 2 includes the subject matter of Example 1, and wherein the NIC is further to generate, by the processor core and in response to having identified that no long-latency operations are to be performed based on the processing of the message, a release message which indicates the network packet can be released to one of the one or more processors or a network interface of the NIC; and transmit, by the processor core, the release message to a memory fabric interface of a memory fabric of the NIC.
  • Example 3 includes the subject matter of any of Examples 1 and 2, and wherein the NIC is further to retrieve, by a job manager of the host interface, an index of a descriptor in a descriptor table stored by a processor of the one or more processors at a location in the memory, wherein the descriptor includes information corresponding to a network packet; forward, by the job manager, a first message to the symmetric multi-purpose (SMP) array of the host interface, wherein the first message includes the index of the descriptor; process, by a first processor core of the plurality of processor cores of the SMP array, the first message to identify the index of the descriptor; generate, by the first processor core, a second message that indicates to perform a fetch operation to retrieve the descriptor based on the index of the descriptor and includes an indication that the retrieved descriptor is to be processed upon retrieval; and forward, by the first processor core, the second message to a DMA engine of the host interface.
  • SMP symmetric multi-purpose
  • Example 4 includes the subject matter of any of Examples 1-3, and wherein the NIC is further to process, by the DMA engine, the second message to identify a DMA fetch operation to be performed, wherein the DMA fetch operation to be performed comprises to fetch the descriptor via DMA; perform, by the DMA engine, the identified DMA fetch operation; generate, by the DMA engine, a third message which includes the descriptor retrieved as a result of the DMA fetch operation, wherein the third message includes a location of the descriptor in a buffer memory of the host interface and the indication that the retrieved descriptor is to be processed; and forward, by the DMA engine, the third message to the SMP array.
  • Example 5 includes the subject matter of any of Examples 1-4, and wherein to forward the first message to the SMP array comprises to enqueue the message in a descriptor queue accessible by the SMP array.
  • Example 6 includes the subject matter of any of Examples 1-5, and wherein to retrieve the index of the descriptor comprises to retrieve the index of the descriptor from a descriptor ring stored in a cache memory of the compute engine.
  • Example 7 includes the subject matter of any of Examples 1-6, and wherein the NIC is further to receive, by the job manager, an authorized traffic limit from a traffic manager of the NIC, wherein the authorized traffic limit indicates an amount of network traffic the job manager is allowed to process upon receipt; retrieve, by the job manager, a next descriptor from the descriptor table; interpret, by the job manager, the next descriptor to determine the amount of network traffic associated with the next descriptor; determine, by the job manager, whether the authorized traffic limit would be exceeded if the network traffic associated with the next descriptor were to be processed as a function of the amount of network traffic associated with the next descriptor and the authorized traffic limit; and return, by the job manager and subsequent to having determined that the authorized traffic limit would be exceeded, the descriptor to the descriptor table.
  • Example 8 includes the subject matter of any of Examples 1-7, and wherein the NIC is further to decrease, by the job manager and subsequent to having determined that the authorized traffic limit would not be exceeded, the authorized traffic limit by the amount of network traffic associated with the next descriptor; generate, by the job manager, a fourth message that includes information usable to locate the descriptor; and insert, by the job manager, the message into a descriptor queue accessible by the SMP array.
  • Example 9 includes the subject matter of any of Examples 1-8, and wherein to retrieve the next descriptor from the descriptor table comprises to perform another DMA fetch operation to return the next descriptor.
  • Example 10 includes the subject matter of any of Examples 1-9, and wherein to retrieve the next descriptor comprises to retrieve the next descriptor associated with one of a header of the network packet, at least a portion of a payload of the network packet, or the header and the payload of the network packet.
  • Example 11 includes the subject matter of any of Examples 1-10, and wherein to identify the long-latency operation comprises to identify a direct memory access (DMA) fetch operation.
  • DMA direct memory access
  • Example 12 includes the subject matter of any of Examples 1-11, and wherein the NIC is further to receive, by an event logic unit of the host interface, an event notification; and build, by the event logic unit, a data structure as a function of a network protocol associated with the event notification, wherein the data structure includes information about the event notification usable by at least one of the plurality of processor cores of the SMP array to process the event notification.
  • Example 13 includes the subject matter of any of Examples 1-12, and wherein to receive the event notification comprises to receive the event notification which indicates one of a signaling event, a memory-mapped input/output event, or a host fabric interface event.
  • Example 14 includes a method for processing network packets, the method comprising retrieving, by a symmetric multi-purpose (SMP) array of a host interface of a network interface controller (NIC) of a compute device, a message from a message queue of the host interface; processing, by a processor core of a plurality of processor cores of the SMP array, the message to identify a long-latency operation to be performed on at least a portion of a network packet associated with the message; generating, by the processor core and in response to having identified the long-latency operation to be performed, another message which includes an indication of the long-latency operation to be performed and a next step to be performed upon completion of the long-latency operation; and transmitting, by the processor core, the other message to a corresponding hardware unit scheduler of the host interface as a function of the long-latency operation to be performed.
  • SMP symmetric multi-purpose
  • NIC network interface controller
  • Example 15 includes the subject matter of Example 14, and further including generating, by the processor core and in response to having identified that no long-latency operations are to be performed based on the processing of the message, a release message which indicates the network packet can be released to one of one or more processors of a compute engine of the compute device or a network interface of the NIC; and transmitting, by the processor core, the release message to a memory fabric interface of a memory fabric of the NIC.
  • Example 16 includes the subject matter of any of Examples 14 and 15, and further including retrieving, by a job manager of the host interface, an index of a descriptor in a descriptor table stored by a processor of one or more processors of a compute engine of the compute device at a location in a memory of the compute engine, wherein the descriptor includes information corresponding to a network packet; forwarding, by the job manager, a first message to the symmetric multi-purpose (SMP) array of the host interface, wherein the first message includes the index of the descriptor; processing, by a first processor core of the plurality of processor cores of the SMP array, the first message to identify the index of the descriptor; generating, by the first processor core, a second message that indicates to perform a fetch operation to retrieve the descriptor based on the index of the descriptor and includes an indication that the retrieved descriptor is to be processed upon retrieval; and forwarding, by the first processor core, the second message to a DMA engine of the host interface.
  • Example 17 includes the subject matter of any of Examples 14-16, and further including processing, by the DMA engine, the second message to identify a DMA fetch operation to be performed, wherein the DMA fetch operation to be performed comprises to fetch the descriptor via DMA; performing, by the DMA engine, the identified DMA fetch operation; generating, by the DMA engine, a third message which includes the descriptor retrieved as a result of the DMA fetch operation, wherein the third message includes a location of the descriptor in a buffer memory of the host interface and the indication that the retrieved descriptor is to be processed; and forwarding, by the DMA engine, the third message to the SMP array.
  • Example 18 includes the subject matter of any of Examples 14-17, and wherein forwarding the first message to the SMP array comprises enqueuing the message in a descriptor queue accessible by the SMP array.
  • Example 19 includes the subject matter of any of Examples 14-18, and wherein retrieving the index of the descriptor comprises retrieving the index of the descriptor from a descriptor ring stored in a cache memory of the compute engine.
  • Example 20 includes the subject matter of any of Examples 14-19, and further including receiving, by the job manager, an authorized traffic limit from a traffic manager of the NIC, wherein the authorized traffic limit indicates an amount of network traffic the job manager is allowed to process upon receipt; retrieving, by the job manager, a next descriptor from the descriptor table; interpreting, by the job manager, the next descriptor to determine the amount of network traffic associated with the next descriptor; determining, by the job manager, whether the authorized traffic limit would be exceeded if the network traffic associated with the next descriptor were to be processed as a function of the amount of network traffic associated with the next descriptor and the authorized traffic limit; and returning, by the job manager and subsequent to having determined that the authorized traffic limit would be exceeded, the descriptor to the descriptor table.
  • Example 21 includes the subject matter of any of Examples 14-20, and further including decreasing, by the job manager and subsequent to having determined that the authorized traffic limit would not be exceeded, the authorized traffic limit by the amount of network traffic associated with the next descriptor; generating, by the job manager, a fourth message that includes information usable to locate the descriptor; and inserting, by the job manager, the message into a descriptor queue accessible by the SMP array.
  • Example 22 includes the subject matter of any of Examples 14-21, and wherein retrieving the next descriptor from the descriptor table comprises performing another DMA fetch operation to return the next descriptor.
  • Example 23 includes the subject matter of any of Examples 14-22, and wherein retrieving the next descriptor comprises retrieving the next descriptor associated with one of a header of the network packet, at least a portion of a payload of the network packet, or the header and the payload of the network packet.
  • Example 24 includes the subject matter of any of Examples 14-23, and wherein identifying the long-latency operation comprises identifying a direct memory access (DMA) fetch operation.
  • DMA direct memory access
  • Example 25 includes the subject matter of any of Examples 14-24, and further including receiving, by an event logic unit of the host interface, an event notification; and building, by the event logic unit, a data structure as a function of a network protocol associated with the event notification, wherein the data structure includes information about the event notification usable by at least one of the plurality of processor cores of the SMP array to process the event notification.
  • Example 26 includes the subject matter of any of Examples 14-25, and wherein receiving the event notification comprises receiving the event notification which indicates one of a signaling event, a memory-mapped input/output event, or a host fabric interface event.
  • Example 27 includes one or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a compute device to perform the method of any of Examples 14-26.
  • Example 28 includes a compute device for improving throughput in a network, the compute device comprising one or more processors; one or more memory devices having stored therein a plurality of instructions that, when executed by the one or more processors, cause the compute device to perform the method of any of Examples 14-26.
  • Example 29 includes a compute device for processing network packets, the compute device comprising host interface circuitry of a network interface controller (NIC) to retrieve, by a symmetric multi-purpose (SMP) array of the host interface circuitry, a message from a message queue of the host interface circuitry; process, by a processor core of a plurality of processor cores of the SMP array, the message to identify a long-latency operation to be performed on at least a portion of a network packet associated with the message; generate, by the processor core and in response to having identified the long-latency operation to be performed, another message which includes an indication of the long-latency operation to be performed and a next step to be performed upon completion of the long-latency operation; and transmit, by the processor core, the other message to a corresponding hardware unit scheduler of the host interface circuitry as a function of the long-latency operation to be performed.
  • NIC network interface controller
  • Example 30 includes the subject matter of Example 29, and wherein the host interface circuitry is further to generate, by the processor core and in response to having identified that no long-latency operations are to be performed based on the processing of the message, a release message which indicates the network packet can be released to one of the one or more processors or a network interface of the NIC; and transmit, by the processor core, the release message to a memory fabric interface of a memory fabric of the NIC.
  • Example 31 includes the subject matter of any of Examples 29 and 30, and wherein the host interface circuitry is further to retrieve, by a job manager of the host interface circuitry, an index of a descriptor in a descriptor table stored by a processor of the one or more processors at a location in the memory, wherein the descriptor includes information corresponding to a network packet; forward, by the job manager, a first message to the symmetric multi-purpose (SMP) array of the host interface circuitry, wherein the first message includes the index of the descriptor; process, by a first processor core of the plurality of processor cores of the SMP array, the first message to identify the index of the descriptor; generate, by the first processor core, a second message that indicates to perform a fetch operation to retrieve the descriptor based on the index of the descriptor and includes an indication that the retrieved descriptor is to be processed upon retrieval; and forward, by the first processor core, the second message to a DMA engine of the host interface circuitry.
  • SMP symmetric
  • Example 32 includes the subject matter of any of Examples 29-31, and wherein the host interface circuitry is further to process, by the DMA engine, the second message to identify a DMA fetch operation to be performed, wherein the DMA fetch operation to be performed comprises to fetch the descriptor via DMA; perform, by the DMA engine, the identified DMA fetch operation; generate, by the DMA engine, a third message which includes the descriptor retrieved as a result of the DMA fetch operation, wherein the third message includes a location of the descriptor in a buffer memory of the host interface circuitry and the indication that the retrieved descriptor is to be processed; and forward, by the DMA engine, the third message to the SMP array.
  • Example 33 includes the subject matter of any of Examples 29-32, and wherein to forward the first message to the SMP array comprises to enqueue the message in a descriptor queue accessible by the SMP array.
  • Example 34 includes the subject matter of any of Examples 29-33, and wherein to retrieve the index of the descriptor comprises to retrieve the index of the descriptor from a descriptor ring stored in a cache memory of the compute engine.
  • Example 35 includes the subject matter of any of Examples 29-34, and wherein the host interface circuitry is further to receive, by the job manager, an authorized traffic limit from a traffic manager of the NIC, wherein the authorized traffic limit indicates an amount of network traffic the job manager is allowed to process upon receipt; retrieve, by the job manager, a next descriptor from the descriptor table; interpret, by the job manager, the next descriptor to determine the amount of network traffic associated with the next descriptor; determine, by the job manager, whether the authorized traffic limit would be exceeded if the network traffic associated with the next descriptor were to be processed as a function of the amount of network traffic associated with the next descriptor and the authorized traffic limit; and return, by the job manager and subsequent to having determined that the authorized traffic limit would be exceeded, the descriptor to the descriptor table.
  • the host interface circuitry is further to receive, by the job manager, an authorized traffic limit from a traffic manager of the NIC, wherein the authorized traffic limit indicates an amount of network traffic the job manager is allowed to process upon receipt;
  • Example 36 includes the subject matter of any of Examples 29-35, and wherein the host interface circuitry is further to decrease, by the job manager and subsequent to having determined that the authorized traffic limit would not be exceeded, the authorized traffic limit by the amount of network traffic associated with the next descriptor; generate, by the job manager, a fourth message that includes information usable to locate the descriptor; and insert, by the job manager, the message into a descriptor queue accessible by the SMP array.
  • Example 37 includes the subject matter of any of Examples 29-36, and wherein to retrieve the next descriptor from the descriptor table comprises to perform another DMA fetch operation to return the next descriptor.
  • Example 38 includes the subject matter of any of Examples 29-37, and wherein to retrieve the next descriptor comprises to retrieve the next descriptor associated with one of a header of the network packet, at least a portion of a payload of the network packet, or the header and the payload of the network packet.
  • Example 39 includes the subject matter of any of Examples 29-38, and wherein to identify the long-latency operation comprises to identify a direct memory access (DMA) fetch operation.
  • DMA direct memory access
  • Example 40 includes the subject matter of any of Examples 29-39, and wherein the host interface circuitry is further to receive, by an event logic unit of the host interface circuitry, an event notification; and build, by the event logic unit, a data structure as a function of a network protocol associated with the event notification, wherein the data structure includes information about the event notification usable by at least one of the plurality of processor cores of the SMP array to process the event notification.
  • Example 41 includes the subject matter of any of Examples 29-40, and wherein to receive the event notification comprises to receive the event notification which indicates one of a signaling event, a memory-mapped input/output event, or a host fabric interface event.
  • Example 42 includes a compute device for processing network packets, the compute device comprising means for retrieving, by a symmetric multi-purpose (SMP) array of a host interface of a network interface controller (NIC) of a compute device, a message from a message queue of the host interface; means for processing, by a processor core of a plurality of processor cores of the SMP array, the message to identify a long-latency operation to be performed on at least a portion of a network packet associated with the message; means for generating, by the processor core and in response to having identified the long-latency operation to be performed, another message which includes an indication of the long-latency operation to be performed and a next step to be performed upon completion of the long-latency operation; and means for transmitting, by the processor core, the other message to a corresponding hardware unit scheduler of the host interface as a function of the long-latency operation to be performed.
  • SMP symmetric multi-purpose
  • NIC network interface controller
  • Example 43 includes the subject matter of Example 42, and further including means for generating, by the processor core and in response to having identified that no long-latency operations are to be performed based on the processing of the message, a release message which indicates the network packet can be released to one of one or more processors of a compute engine of the compute device or a network interface of the NIC; and means for transmitting, by the processor core, the release message to a memory fabric interface of a memory fabric of the NIC.
  • Example 44 includes the subject matter of any of Examples 42 and 43, and further including means for retrieving, by a job manager of the host interface, an index of a descriptor in a descriptor table stored by a processor of one or more processors of a compute engine of the compute device at a location in a memory of the compute engine, wherein the descriptor includes information corresponding to a network packet; means for forwarding, by the job manager, a first message to the symmetric multi-purpose (SMP) array of the host interface, wherein the first message includes the index of the descriptor; means for processing, by a first processor core of the plurality of processor cores of the SMP array, the first message to identify the index of the descriptor; means for generating, by the first processor core, a second message that indicates to perform a fetch operation to retrieve the descriptor based on the index of the descriptor and includes an indication that the retrieved descriptor is to be processed upon retrieval; and means for forwarding, by the first processor core, the second message to a
  • Example 45 includes the subject matter of any of Examples 42-44, and further including means for processing, by the DMA engine, the second message to identify a DMA fetch operation to be performed, wherein the DMA fetch operation to be performed comprises to fetch the descriptor via DMA; means for performing, by the DMA engine, the identified DMA fetch operation; means for generating, by the DMA engine, a third message which includes the descriptor retrieved as a result of the DMA fetch operation, wherein the third message includes a location of the descriptor in a buffer memory of the host interface and the indication that the retrieved descriptor is to be processed; and means for forwarding, by the DMA engine, the third message to the SMP array.
  • Example 46 includes the subject matter of any of Examples 42-45, and wherein the means for forwarding the first message to the SMP array comprises means for enqueuing the message in a descriptor queue accessible by the SMP array.
  • Example 47 includes the subject matter of any of Examples 42-46, and wherein the means for retrieving the index of the descriptor comprises means for retrieving the index of the descriptor from a descriptor ring stored in a cache memory of the compute engine.
  • Example 48 includes the subject matter of any of Examples 42-47, and further including means for receiving, by the job manager, an authorized traffic limit from a traffic manager of the NIC, wherein the authorized traffic limit indicates an amount of network traffic the job manager is allowed to process upon receipt; means for retrieving, by the job manager, a next descriptor from the descriptor table; means for interpreting, by the job manager, the next descriptor to determine the amount of network traffic associated with the next descriptor; means for determining, by the job manager, whether the authorized traffic limit would be exceeded if the network traffic associated with the next descriptor were to be processed as a function of the amount of network traffic associated with the next descriptor and the authorized traffic limit; and means for returning, by the job manager and subsequent to having determined that the authorized traffic limit would be exceeded, the descriptor to the descriptor table.
  • Example 49 includes the subject matter of any of Examples 42-48, and further including means for decreasing, by the job manager and subsequent to having determined that the authorized traffic limit would not be exceeded, the authorized traffic limit by the amount of network traffic associated with the next descriptor; means for generating, by the job manager, a fourth message that includes information usable to locate the descriptor; and means for inserting, by the job manager, the message into a descriptor queue accessible by the SMP array.
  • Example 50 includes the subject matter of any of Examples 42-49, and wherein the means for retrieving the next descriptor from the descriptor table comprises means for performing another DMA fetch operation to return the next descriptor.
  • Example 51 includes the subject matter of any of Examples 42-50, and wherein the means for retrieving the next descriptor comprises means for retrieving the next descriptor associated with one of a header of the network packet, at least a portion of a payload of the network packet, or the header and the payload of the network packet.
  • Example 52 includes the subject matter of any of Examples 42-51, and wherein the means for identifying the long-latency operation comprises means for identifying a direct memory access (DMA) fetch operation.
  • DMA direct memory access
  • Example 53 includes the subject matter of any of Examples 42-52, and further including means for receiving, by an event logic unit of the host interface, an event notification; and means for building, by the event logic unit, a data structure as a function of a network protocol associated with the event notification, wherein the data structure includes information about the event notification usable by at least one of the plurality of processor cores of the SMP array to process the event notification.
  • Example 54 includes the subject matter of any of Examples 42-53, and wherein the means for receiving the event notification comprises means for receiving the event notification which indicates one of a signaling event, a memory-mapped input/output event, or a host fabric interface event.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Software Systems (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Human Computer Interaction (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Quality & Reliability (AREA)
  • Computational Linguistics (AREA)
  • Mathematical Physics (AREA)
  • Thermal Sciences (AREA)
  • Computing Systems (AREA)
  • Geometry (AREA)
  • Evolutionary Computation (AREA)
  • Environmental & Geological Engineering (AREA)
  • Cooling Or The Like Of Electrical Apparatus (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Multi Processors (AREA)
  • Robotics (AREA)
  • Mechanical Engineering (AREA)
  • Power Engineering (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Debugging And Monitoring (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)
  • Small-Scale Networks (AREA)
  • Optical Communication System (AREA)
US15/833,523 2017-08-30 2017-12-06 Technologies for managing a flexible host interface of a network interface controller Abandoned US20190044809A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US15/833,523 US20190044809A1 (en) 2017-08-30 2017-12-06 Technologies for managing a flexible host interface of a network interface controller
DE102018212479.5A DE102018212479A1 (de) 2017-08-30 2018-07-26 Technologien zum Verwalten einer flexiblen Host-Schnittstelle eines Netzwerkschnittstellen-Controllers
CN202110870167.3A CN113806260B (zh) 2017-08-30 2018-08-30 用于管理网络接口控制器的灵活主机接口的技术
CN201811004869.8A CN109426633A (zh) 2017-08-30 2018-08-30 用于管理网络接口控制器的灵活主机接口的技术
CN202311445788.2A CN117725004A (zh) 2017-08-30 2018-08-30 用于管理网络接口控制器的灵活主机接口的技术
US17/344,253 US11843691B2 (en) 2017-08-30 2021-06-10 Technologies for managing a flexible host interface of a network interface controller
US18/241,748 US20230412365A1 (en) 2017-08-30 2023-09-01 Technologies for managing a flexible host interface of a network interface controller

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
IN201741030632 2017-08-30
IN201741030632 2017-08-30
US201762584401P 2017-11-10 2017-11-10
US15/833,523 US20190044809A1 (en) 2017-08-30 2017-12-06 Technologies for managing a flexible host interface of a network interface controller

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/344,253 Continuation US11843691B2 (en) 2017-08-30 2021-06-10 Technologies for managing a flexible host interface of a network interface controller

Publications (1)

Publication Number Publication Date
US20190044809A1 true US20190044809A1 (en) 2019-02-07

Family

ID=65037934

Family Applications (26)

Application Number Title Priority Date Filing Date
US15/833,523 Abandoned US20190044809A1 (en) 2017-08-30 2017-12-06 Technologies for managing a flexible host interface of a network interface controller
US15/856,556 Expired - Fee Related US10567166B2 (en) 2017-08-30 2017-12-28 Technologies for dividing memory across socket partitions
US15/856,644 Expired - Fee Related US10728024B2 (en) 2017-08-30 2017-12-28 Technologies for providing runtime code in an option ROM
US15/856,173 Active 2038-03-05 US10469252B2 (en) 2017-08-30 2017-12-28 Technologies for efficiently managing allocation of memory in a shared memory pool
US15/856,220 Active 2038-02-10 US10554391B2 (en) 2017-08-30 2017-12-28 Technologies for dynamically allocating data storage capacity for different data storage types
US15/856,858 Abandoned US20190034490A1 (en) 2017-08-30 2017-12-28 Technologies for structured database query
US15/858,569 Abandoned US20190042126A1 (en) 2017-08-30 2017-12-29 Technologies for storage discovery and reallocation
US15/859,369 Active US10476670B2 (en) 2017-08-30 2017-12-30 Technologies for providing remote access to a shared memory pool
US15/859,387 Active 2039-08-29 US11050554B2 (en) 2017-08-30 2017-12-30 Technologies for managing exact match hash table growth
US15/859,391 Active 2040-06-07 US11249816B2 (en) 2017-08-30 2017-12-30 Pivot rack
US15/859,367 Active 2038-05-02 US10581596B2 (en) 2017-08-30 2017-12-30 Technologies for managing errors in a remotely accessible memory pool
US15/868,492 Abandoned US20190042408A1 (en) 2017-08-30 2018-01-11 Technologies for interleaving memory across shared memory pools
US15/868,594 Abandoned US20190042611A1 (en) 2017-08-30 2018-01-11 Technologies for structured database query for finding unique element values
US15/912,733 Active 2039-08-23 US11025411B2 (en) 2017-08-30 2018-03-06 Technologies for providing streamlined provisioning of accelerated functions in a disaggregated architecture
US15/922,502 Abandoned US20190042091A1 (en) 2017-08-30 2018-03-15 Technologies for providing efficient distributed data storage in a disaggregated architecture
US15/922,493 Abandoned US20190042090A1 (en) 2017-08-30 2018-03-15 Technologies for separating control plane management from data plane management for distributed storage in a disaggregated architecture
US15/941,114 Abandoned US20190052457A1 (en) 2017-08-30 2018-03-30 Technologies for providing efficient sharing of encrypted data in a disaggregated architecture
US16/045,345 Active US10756886B2 (en) 2017-08-30 2018-07-25 Technologies for load balancing a network
US17/001,502 Active 2038-09-30 US11588624B2 (en) 2017-08-30 2020-08-24 Technologies for load balancing a network
US17/332,733 Active 2038-03-14 US11522682B2 (en) 2017-08-30 2021-05-27 Technologies for providing streamlined provisioning of accelerated functions in a disaggregated architecture
US17/344,253 Active 2038-08-11 US11843691B2 (en) 2017-08-30 2021-06-10 Technologies for managing a flexible host interface of a network interface controller
US17/391,549 Abandoned US20220012105A1 (en) 2017-08-30 2021-08-02 Technologies for allocating resources across data centers
US17/871,429 Active 2038-04-02 US11888967B2 (en) 2017-08-30 2022-07-22 Technologies for dynamic accelerator selection
US18/238,096 Pending US20230421358A1 (en) 2017-08-30 2023-08-25 Technologies for allocating resources across data centers
US18/241,748 Pending US20230412365A1 (en) 2017-08-30 2023-09-01 Technologies for managing a flexible host interface of a network interface controller
US18/542,308 Pending US20240195605A1 (en) 2017-08-30 2023-12-15 Technologies for dynamic accelerator selection

Family Applications After (25)

Application Number Title Priority Date Filing Date
US15/856,556 Expired - Fee Related US10567166B2 (en) 2017-08-30 2017-12-28 Technologies for dividing memory across socket partitions
US15/856,644 Expired - Fee Related US10728024B2 (en) 2017-08-30 2017-12-28 Technologies for providing runtime code in an option ROM
US15/856,173 Active 2038-03-05 US10469252B2 (en) 2017-08-30 2017-12-28 Technologies for efficiently managing allocation of memory in a shared memory pool
US15/856,220 Active 2038-02-10 US10554391B2 (en) 2017-08-30 2017-12-28 Technologies for dynamically allocating data storage capacity for different data storage types
US15/856,858 Abandoned US20190034490A1 (en) 2017-08-30 2017-12-28 Technologies for structured database query
US15/858,569 Abandoned US20190042126A1 (en) 2017-08-30 2017-12-29 Technologies for storage discovery and reallocation
US15/859,369 Active US10476670B2 (en) 2017-08-30 2017-12-30 Technologies for providing remote access to a shared memory pool
US15/859,387 Active 2039-08-29 US11050554B2 (en) 2017-08-30 2017-12-30 Technologies for managing exact match hash table growth
US15/859,391 Active 2040-06-07 US11249816B2 (en) 2017-08-30 2017-12-30 Pivot rack
US15/859,367 Active 2038-05-02 US10581596B2 (en) 2017-08-30 2017-12-30 Technologies for managing errors in a remotely accessible memory pool
US15/868,492 Abandoned US20190042408A1 (en) 2017-08-30 2018-01-11 Technologies for interleaving memory across shared memory pools
US15/868,594 Abandoned US20190042611A1 (en) 2017-08-30 2018-01-11 Technologies for structured database query for finding unique element values
US15/912,733 Active 2039-08-23 US11025411B2 (en) 2017-08-30 2018-03-06 Technologies for providing streamlined provisioning of accelerated functions in a disaggregated architecture
US15/922,502 Abandoned US20190042091A1 (en) 2017-08-30 2018-03-15 Technologies for providing efficient distributed data storage in a disaggregated architecture
US15/922,493 Abandoned US20190042090A1 (en) 2017-08-30 2018-03-15 Technologies for separating control plane management from data plane management for distributed storage in a disaggregated architecture
US15/941,114 Abandoned US20190052457A1 (en) 2017-08-30 2018-03-30 Technologies for providing efficient sharing of encrypted data in a disaggregated architecture
US16/045,345 Active US10756886B2 (en) 2017-08-30 2018-07-25 Technologies for load balancing a network
US17/001,502 Active 2038-09-30 US11588624B2 (en) 2017-08-30 2020-08-24 Technologies for load balancing a network
US17/332,733 Active 2038-03-14 US11522682B2 (en) 2017-08-30 2021-05-27 Technologies for providing streamlined provisioning of accelerated functions in a disaggregated architecture
US17/344,253 Active 2038-08-11 US11843691B2 (en) 2017-08-30 2021-06-10 Technologies for managing a flexible host interface of a network interface controller
US17/391,549 Abandoned US20220012105A1 (en) 2017-08-30 2021-08-02 Technologies for allocating resources across data centers
US17/871,429 Active 2038-04-02 US11888967B2 (en) 2017-08-30 2022-07-22 Technologies for dynamic accelerator selection
US18/238,096 Pending US20230421358A1 (en) 2017-08-30 2023-08-25 Technologies for allocating resources across data centers
US18/241,748 Pending US20230412365A1 (en) 2017-08-30 2023-09-01 Technologies for managing a flexible host interface of a network interface controller
US18/542,308 Pending US20240195605A1 (en) 2017-08-30 2023-12-15 Technologies for dynamic accelerator selection

Country Status (5)

Country Link
US (26) US20190044809A1 (de)
EP (5) EP3823245A1 (de)
JP (1) JP7214394B2 (de)
CN (13) CN109426455A (de)
DE (1) DE102018212479A1 (de)

Cited By (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200097427A1 (en) * 2018-09-25 2020-03-26 International Business Machines Corporation Efficient component communication through protocol switching in disaggregated datacenters
US10785549B2 (en) 2016-07-22 2020-09-22 Intel Corporation Technologies for switching network traffic in a data center
US10802988B2 (en) 2018-09-25 2020-10-13 International Business Machines Corporation Dynamic memory-based communication in disaggregated datacenters
US10831698B2 (en) 2018-09-25 2020-11-10 International Business Machines Corporation Maximizing high link bandwidth utilization through efficient component communication in disaggregated datacenters
WO2020236274A1 (en) * 2019-05-23 2020-11-26 Cray Inc. System and method for facilitating efficient event notification management for a network interface controller (nic)
US10911358B1 (en) * 2017-09-26 2021-02-02 Amazon Technologies, Inc. Packet processing cache
US10915493B2 (en) 2018-09-25 2021-02-09 International Business Machines Corporation Component building blocks and optimized compositions thereof in disaggregated datacenters
US10983985B2 (en) * 2018-10-29 2021-04-20 International Business Machines Corporation Determining a storage pool to store changed data objects indicated in a database
US11012423B2 (en) 2018-09-25 2021-05-18 International Business Machines Corporation Maximizing resource utilization through efficient component communication in disaggregated datacenters
US11023155B2 (en) 2018-10-29 2021-06-01 International Business Machines Corporation Processing event messages for changed data objects to determine a storage pool to store the changed data objects
US11088967B2 (en) * 2019-04-26 2021-08-10 Intel Corporation Shared resources for multiple communication traffics
US11137922B2 (en) 2016-11-29 2021-10-05 Intel Corporation Technologies for providing accelerated functions as a service in a disaggregated architecture
US11182322B2 (en) 2018-09-25 2021-11-23 International Business Machines Corporation Efficient component communication through resource rewiring in disaggregated datacenters
US20220103478A1 (en) * 2020-09-28 2022-03-31 Vmware, Inc. Flow processing offload using virtual port identifiers
US11376934B2 (en) 2019-05-20 2022-07-05 Mountain Top Industries Aps Lid arrangement for a canister for a rollup truck bed cover
US11409900B2 (en) 2018-11-15 2022-08-09 International Business Machines Corporation Processing event messages for data objects in a message queue to determine data to redact
US11429674B2 (en) 2018-11-15 2022-08-30 International Business Machines Corporation Processing event messages for data objects to determine data to redact from a database
US11444890B2 (en) * 2018-01-28 2022-09-13 Drivenets Ltd. Method and device for improving bandwidth utilization in a communication network
JP2022539845A (ja) * 2019-07-11 2022-09-13 北京字節跳動網絡技術有限公司 適応ループフィルタリングにおけるサンプルパディング
US11483246B2 (en) 2020-01-13 2022-10-25 Vmware, Inc. Tenant-specific quality of service
US11539633B2 (en) 2020-08-31 2022-12-27 Vmware, Inc. Determining whether to rate limit traffic
US11593278B2 (en) 2020-09-28 2023-02-28 Vmware, Inc. Using machine executing on a NIC to access a third party storage not supported by a NIC or host
US20230067118A1 (en) * 2021-09-02 2023-03-02 Baidu Usa Llc Rack systems and packaging for servers
US11599395B2 (en) * 2020-02-19 2023-03-07 Vmware, Inc. Dynamic core allocation
TWI797627B (zh) * 2020-09-16 2023-04-01 日商鎧俠股份有限公司 通訊系統、記憶體元件及通訊方法
US11636053B2 (en) 2020-09-28 2023-04-25 Vmware, Inc. Emulating a local storage by accessing an external storage through a shared port of a NIC
US11650849B2 (en) 2018-09-25 2023-05-16 International Business Machines Corporation Efficient component communication through accelerator switching in disaggregated datacenters
US20230214337A1 (en) * 2022-01-06 2023-07-06 Vmware, Inc. Methods and systems for extablishing direct communications between a server computer and a smart network interface controller
US11716383B2 (en) 2020-09-28 2023-08-01 Vmware, Inc. Accessing multiple external storages to present an emulated local storage through a NIC
US11799784B2 (en) 2021-06-08 2023-10-24 Vmware, Inc. Virtualized QoS support in software defined networks
US11829793B2 (en) 2020-09-28 2023-11-28 Vmware, Inc. Unified management of virtual machines and bare metal computers
US11831869B2 (en) 2019-07-09 2023-11-28 Beijing Bytedance Network Technology Co., Ltd. Sample determination for adaptive loop filtering
US11863376B2 (en) 2021-12-22 2024-01-02 Vmware, Inc. Smart NIC leader election
US11871547B2 (en) 2021-09-02 2024-01-09 Baidu Usa Llc Two phase system for enclosure systems
US20240020357A1 (en) * 2022-07-15 2024-01-18 Vmware, Inc. Keyless licensing in a multi-cloud computing system
US11899594B2 (en) 2022-06-21 2024-02-13 VMware LLC Maintenance of data message classification cache on smart NIC
US11928062B2 (en) 2022-06-21 2024-03-12 VMware LLC Accelerating data message classification with smart NICs
US11928367B2 (en) 2022-06-21 2024-03-12 VMware LLC Logical memory addressing for network devices
US11962518B2 (en) 2020-06-02 2024-04-16 VMware LLC Hardware acceleration techniques using flow selection
US11995024B2 (en) 2021-12-22 2024-05-28 VMware LLC State sharing between smart NICs
US12021759B2 (en) 2020-09-28 2024-06-25 VMware LLC Packet processing with hardware offload units
EP4283468A4 (de) * 2021-03-11 2024-07-10 Huawei Tech Co Ltd Datenübertragungssystem und zugehörige vorrichtung

Families Citing this family (110)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9367562B2 (en) 2013-12-05 2016-06-14 Google Inc. Distributing data on distributed storage systems
US9448887B1 (en) * 2015-08-22 2016-09-20 Weka.IO Ltd. Distributed erasure coded virtual file system
EP3549350A4 (de) * 2016-11-29 2021-03-24 Intel Corporation Technologien für millimeterwellen-rack-verbindungen
US10534598B2 (en) * 2017-01-04 2020-01-14 International Business Machines Corporation Rolling upgrades in disaggregated systems
US11153164B2 (en) 2017-01-04 2021-10-19 International Business Machines Corporation Live, in-line hardware component upgrades in disaggregated systems
WO2018173164A1 (ja) * 2017-03-22 2018-09-27 株式会社日立製作所 データ処理システム
US11030126B2 (en) * 2017-07-14 2021-06-08 Intel Corporation Techniques for managing access to hardware accelerator memory
US20190044809A1 (en) * 2017-08-30 2019-02-07 Intel Corporation Technologies for managing a flexible host interface of a network interface controller
US10726930B2 (en) 2017-10-06 2020-07-28 Western Digital Technologies, Inc. Method and system for a storage (SSD) drive-level failure and health prediction leveraging machine learning on internal parametric data
JP6757708B2 (ja) * 2017-10-31 2020-09-23 株式会社日立製作所 情報処理装置及び構成要素の管理方法
US11262912B2 (en) * 2017-11-13 2022-03-01 Weka.IO Ltd. File operations in a distributed storage system
US11050574B2 (en) * 2017-11-29 2021-06-29 Taiwan Semiconductor Manufacturing Company, Ltd. Authentication based on physically unclonable functions
US11317542B2 (en) 2017-12-30 2022-04-26 Intel Corporation Technologies for improving processor thermal design power
US10635609B2 (en) 2018-03-02 2020-04-28 Samsung Electronics Co., Ltd. Method for supporting erasure code data protection with embedded PCIE switch inside FPGA+SSD
US20240095196A1 (en) * 2018-03-02 2024-03-21 Samsung Electronics Co., Ltd. Method for supporting erasure code data protection with embedded pcie switch inside fpga+ssd
US10990554B2 (en) 2018-03-02 2021-04-27 Samsung Electronics Co., Ltd. Mechanism to identify FPGA and SSD pairing in a multi-device environment
US10838647B2 (en) * 2018-03-14 2020-11-17 Intel Corporation Adaptive data migration across disaggregated memory resources
US10579548B2 (en) * 2018-03-29 2020-03-03 Western Digital Technologies, Inc. Adaptive interleaving of data transfer requests
US11108697B2 (en) * 2018-03-30 2021-08-31 Intel Corporation Technologies for controlling jitter at network packet egress
US11062045B2 (en) * 2018-04-13 2021-07-13 Mastercard International Incorporated Computer-implemented methods, systems comprising computer-readable media, and electronic devices for propagating access to assets across a plurality of datasources
US11330042B2 (en) * 2018-05-17 2022-05-10 International Business Machines Corporation Optimizing dynamic resource allocations for storage-dependent workloads in disaggregated data centers
US10552185B2 (en) * 2018-05-24 2020-02-04 International Business Machines Corporation Lightweight and precise value profiling
US10656990B2 (en) * 2018-06-13 2020-05-19 Nutanix, Inc. Dynamically adjusting reserve portion and allocation portions of disaster recovery site in a virtual computing system
US10846070B2 (en) * 2018-07-05 2020-11-24 At&T Intellectual Property I, L.P. Facilitating cloud native edge computing via behavioral intelligence
US10831411B2 (en) * 2018-07-24 2020-11-10 International Business Machines Corporation Storage controller with OCS for managing active-passive backend storage arrays
US11586514B2 (en) * 2018-08-13 2023-02-21 Stratus Technologies Ireland Ltd. High reliability fault tolerant computer architecture
CN109325494B (zh) * 2018-08-27 2021-09-17 腾讯科技（深圳）有限公司 图片处理方法、任务数据处理方法和装置
US10901893B2 (en) * 2018-09-28 2021-01-26 International Business Machines Corporation Memory bandwidth management for performance-sensitive IaaS
US11096284B2 (en) * 2018-10-01 2021-08-17 Intel Corporation Compact semiconductor chip system and method
US11379488B2 (en) * 2018-11-07 2022-07-05 Sap Se Energy-efficient decay algorithm for non-volatile memories
FR3092218B1 (fr) * 2019-01-28 2023-12-22 Ateme Procédé de communication de données, et système pour la mise en œuvre du procédé
US10990517B1 (en) * 2019-01-28 2021-04-27 Xilinx, Inc. Configurable overlay on wide memory channels for efficient memory access
US11023324B2 (en) * 2019-01-31 2021-06-01 EMC IP Holding Company LLC Harmonization of failure domains in a distributed system
US10983948B2 (en) * 2019-03-07 2021-04-20 Raytheon Company Reconfigurable computing appliance
JP7305990B2 (ja) * 2019-03-12 2023-07-11 富士通株式会社 転送プログラム、転送方法、および情報処理装置
US20190235773A1 (en) * 2019-04-09 2019-08-01 Mark Schmisseur Concept for accessing computer memory of a memory pool
SG11202111158SA (en) * 2019-04-25 2021-11-29 Liveperson Inc Smart capacity for workload routing
US11397653B2 (en) 2019-05-29 2022-07-26 Intel Corporation Technologies for fast recovery of distributed storage systems on disaggregated storage
US10970309B2 (en) * 2019-06-05 2021-04-06 Advanced New Technologies Co., Ltd. Data storage method and apparatus
CN110209249A (zh) * 2019-06-06 2019-09-06 英业达科技有限公司 服务器的机壳
JP7151631B2 (ja) * 2019-06-11 2022-10-12 株式会社デンソー 車両用制御装置、車両用表示システム、及び車両用表示制御方法
US11074177B2 (en) * 2019-06-19 2021-07-27 Micron Technology, Inc. Garbage collection adapted to host write activity
US11163482B2 (en) 2019-06-26 2021-11-02 International Business Machines Corporation Dynamic performance-class adjustment for storage drives
US11049570B2 (en) * 2019-06-26 2021-06-29 International Business Machines Corporation Dynamic writes-per-day adjustment for storage drives
US11137915B2 (en) 2019-06-27 2021-10-05 International Business Machines Corporation Dynamic logical storage capacity adjustment for storage drives
US10949362B2 (en) * 2019-06-28 2021-03-16 Intel Corporation Technologies for facilitating remote memory requests in accelerator devices
US11803773B2 (en) * 2019-07-30 2023-10-31 EMC IP Holding Company LLC Machine learning-based anomaly detection using time series decomposition
US10925166B1 (en) * 2019-08-07 2021-02-16 Quanta Computer Inc. Protection fixture
US11283635B2 (en) * 2019-09-28 2022-03-22 Intel Corporation Dynamic sharing in secure memory environments using edge service sidecars
US11550617B2 (en) 2019-10-16 2023-01-10 Intel Corporation Disaggregated rack mount storage side transaction support
US12086446B2 (en) 2019-10-21 2024-09-10 Intel Corporation Memory and storage pool interfaces
US11782810B2 (en) * 2019-11-22 2023-10-10 Dell Products, L.P. Systems and methods for automated field replacement component configuration
US11861219B2 (en) 2019-12-12 2024-01-02 Intel Corporation Buffer to reduce write amplification of misaligned write operations
EP4085594B1 (de) * 2020-01-02 2024-09-18 Sandpiper CDN, LLC System und verfahren zur speicherung von inhaltsdaten in einem sekundären speicher
US11561916B2 (en) * 2020-01-13 2023-01-24 Hewlett Packard Enterprise Development Lp Processing task deployment in adapter devices and accelerators
US11275705B2 (en) * 2020-01-28 2022-03-15 Dell Products L.P. Rack switch coupling system
US11989135B2 (en) * 2020-02-10 2024-05-21 Intel Corporation Programmable address range engine for larger region sizes
US10853548B1 (en) * 2020-02-11 2020-12-01 Capital One Services, Llc Reconfiguration of hardware components of an integrated circuit
US11436367B2 (en) 2020-02-25 2022-09-06 Hewlett Packard Enterprise Development Lp Pre-operating system environment-based sanitization of storage devices
US11115497B2 (en) * 2020-03-25 2021-09-07 Intel Corporation Technologies for providing advanced resource management in a disaggregated environment
US11509079B2 (en) * 2020-04-06 2022-11-22 Hewlett Packard Enterprise Development Lp Blind mate connections with different sets of datums
US11360681B2 (en) * 2020-05-27 2022-06-14 Xiaoliang Zhao Systems and methods for scalable shared memory among networked devices comprising IP addressable memory blocks
US11522917B2 (en) * 2020-06-10 2022-12-06 Arista Networks, Inc. Scalable network processing segmentation
US11853798B2 (en) * 2020-09-03 2023-12-26 Microsoft Technology Licensing, Llc Disaggregated memory pool assignment
US20220103290A1 (en) * 2020-09-29 2022-03-31 Qualcomm Incorporated Interleaver design for noncoherent reed muller codes
DE102020214951A1 (de) * 2020-11-27 2022-06-02 Robert Bosch Gesellschaft mit beschränkter Haftung Verfahren zum dynamischen Zuweisen von Speicherbandbreite
US11392740B2 (en) * 2020-12-18 2022-07-19 SambaNova Systems, Inc. Dataflow function offload to reconfigurable processors
US20220231933A1 (en) * 2021-01-20 2022-07-21 Nvidia Corporation Performing network congestion control utilizing reinforcement learning
JP2024504171A (ja) * 2021-01-25 2024-01-30 ボリュームズ テクノロジーズ リミテッド オペレーティングシステムベースのストレージ方法およびシステム
CN114911725A (zh) * 2021-02-10 2022-08-16 华为技术有限公司 通信方法、装置及系统
US11509590B2 (en) * 2021-02-17 2022-11-22 Juniper Networks, Inc. Determining network device statistics associated with fast counters and slow counters
US11785735B2 (en) * 2021-02-19 2023-10-10 CyberSecure IPS, LLC Intelligent cable patching of racks to facilitate cable installation
US11863613B1 (en) * 2021-03-22 2024-01-02 Amazon Technologies, Inc. Allocation of workloads in dynamic worker fleet
CN117203615A (zh) 2021-04-09 2023-12-08 微软技术许可有限责任公司 经由分发扩展主机策略
US11799785B2 (en) 2021-04-09 2023-10-24 Microsoft Technology Licensing, Llc Hardware-based packet flow processing
US11757782B2 (en) * 2021-04-09 2023-09-12 Microsoft Technology Licensing, Llc Architectures for disaggregating SDN from the host
CN113127173B (zh) * 2021-04-21 2021-09-24 浙江大学 一种异构感知的集群调度方法及装置
US20220361354A1 (en) * 2021-05-10 2022-11-10 Vertiv It Systems, Inc. Supplemental component mounting platform for equipment rack
CN113347230B (zh) * 2021-05-13 2022-09-06 长沙星融元数据技术有限公司 基于可编程交换机的负载均衡方法、装置、设备及介质
US20210271517A1 (en) * 2021-05-19 2021-09-02 Intel Corporation Resource selection based in part on workload
US11537457B2 (en) * 2021-06-25 2022-12-27 Intel Corporation Low latency remoting to accelerators
US20220417138A1 (en) * 2021-06-25 2022-12-29 Oracle International Corporation Routing policies for graphical processing units
US11669529B2 (en) * 2021-07-13 2023-06-06 Capital One Services, Llc Dynamic query allocation to virtual warehouses
US11494413B1 (en) 2021-07-13 2022-11-08 Capital One Services, Llc Query alerts generation for virtual warehouse
US11914595B2 (en) 2021-07-13 2024-02-27 Capital One Services, Llc Virtual warehouse query monitoring and reporting
US11825354B2 (en) * 2021-08-04 2023-11-21 Dish Wireless L.L.C. Customer specific network slicing
US20230046403A1 (en) * 2021-08-11 2023-02-16 International Business Machines Corporation Multi-device processing activity allocation
US20220014551A1 (en) * 2021-09-24 2022-01-13 Intel Corporation Method and apparatus to reduce risk of denial of service resource acquisition attacks in a data center
US20230112448A1 (en) * 2021-10-12 2023-04-13 Seagate Technology Llc Computational storage drive using fpga implemented interface
US11650745B1 (en) * 2021-10-29 2023-05-16 Oracle International Corporation Increased data processing performance of a non-volatile memory express (NVME) block store
KR20230064849A (ko) * 2021-11-04 2023-05-11 에스케이하이닉스 주식회사 스토리지 장치 및 그 동작 방법
US11880568B2 (en) 2021-11-17 2024-01-23 Seagate Technology Llc On demand configuration of FPGA interfaces
US11954345B2 (en) * 2021-12-03 2024-04-09 Samsung Electronics Co., Ltd. Two-level indexing for key-value persistent storage device
US20220116487A1 (en) * 2021-12-20 2022-04-14 Intel Corporation Method and apparatus to perform operations on multiple segments of a data packet in a network interface controller
US11934255B2 (en) * 2022-01-04 2024-03-19 Bank Of America Corporation System and method for improving memory resource allocations in database blocks for executing tasks
US11842179B2 (en) 2022-01-07 2023-12-12 Dell Products L.P. System for automatically generating customer specific data center application program interfaces
US11924029B2 (en) 2022-01-07 2024-03-05 Dell Products L.P. System for scoring data center application program interfaces
US11922229B2 (en) 2022-01-10 2024-03-05 Dell Products L.P. System for determining data center application program interface readiness
US11593189B1 (en) * 2022-01-14 2023-02-28 Dell Products L.P. Configuring new storage systems based on write endurance
US11848835B2 (en) * 2022-01-20 2023-12-19 Dell Products L.P. System for quantifying data center infrastructure utilization units
KR102711804B1 (ko) * 2022-01-26 2024-10-02 한국전자통신연구원 확장 메모리 풀의 리프레시 주기 조절 방법 및 장치
CN114442792A (zh) * 2022-02-09 2022-05-06 北京小米移动软件有限公司 处理器的运行频率调整方法、装置及存储介质
US20230038307A1 (en) * 2022-04-06 2023-02-09 Intel Corporation Network interface device feedback for adaptive and failover multipath routing
US11924115B2 (en) * 2022-05-20 2024-03-05 Ipco 2012 Limited Systems and methods for use in balancing network resources
US20240037029A1 (en) * 2022-07-27 2024-02-01 Hewlett Packard Enterprise Development Lp Client allocation of memory across memory servers
CN115130666B (zh) * 2022-08-31 2022-11-22 之江实验室 一种二维光子卷积加速方法和系统
KR20240059347A (ko) * 2022-10-27 2024-05-07 삼성전자주식회사 메모리 공간 할당 방법, 장치 및 시스템
US20240163171A1 (en) * 2022-11-08 2024-05-16 Dell Products L.P. Logical network resource allocation and creation
US12132632B2 (en) * 2022-11-18 2024-10-29 Dell Products L.P. Unified performance metric for identifying data center utilization
CN117200422B (zh) * 2023-11-08 2024-03-19 深圳市胜威南方科技有限公司 一种通讯系统供电用的pdu供电设备

Family Cites Families (239)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3583625A (en) 1968-10-25 1971-06-08 Gabriel Gero Cigarette dispensing package
US4258967A (en) * 1979-11-02 1981-03-31 Digital Equipment Corporation Integral pivot and lock apparatus for slide rack mounted boxes
JPH0731402Y2 (ja) * 1987-06-15 1995-07-19 パイオニア株式会社 カートリッジ収納ディスク再生装置
JPS6450274A (en) * 1987-08-21 1989-02-27 Pioneer Electronic Corp Auto-changer type disk player
EP0335555B1 (de) * 1988-03-31 1995-08-23 AT&T Corp. Schnittstellenprotokoll zwischen Benutzer und Netz für einen Paketkommunikationsnetz
US5123045A (en) * 1989-08-18 1992-06-16 Massachusetts Institute Of Technology Comprehensive software protection system
US5226714A (en) * 1992-05-26 1993-07-13 Wright Jack V Pivoting drawer slide system
JP3215237B2 (ja) * 1993-10-01 2001-10-02 富士通株式会社 記憶装置および記憶装置の書き込み／消去方法
US5469335A (en) * 1994-11-14 1995-11-21 Compaq Computer Corporation Power distribution connector apparatus for back-to-back sandwiched circuit boards
US5584396A (en) * 1995-05-17 1996-12-17 Dell Usa Lp Sliding pivoting storage apparatus
US6179489B1 (en) * 1997-04-04 2001-01-30 Texas Instruments Incorporated Devices, methods, systems and software products for coordination of computer main microprocessor and second microprocessor coupled thereto
US5822582A (en) * 1996-07-19 1998-10-13 Compaq Computer Corporation Boot drive selection and hibernation file detection
US6105119A (en) * 1997-04-04 2000-08-15 Texas Instruments Incorporated Data transfer circuitry, DSP wrapper circuitry and improved processor devices, methods and systems
US6298370B1 (en) * 1997-04-04 2001-10-02 Texas Instruments Incorporated Computer operating process allocating tasks between first and second processors at run time based upon current processor load
US5974518A (en) * 1997-04-10 1999-10-26 Milgo Solutions, Inc. Smart buffer size adaptation apparatus and method
US6181549B1 (en) * 1997-06-24 2001-01-30 Dell Products, L.P. Chassis retaining system for an electronics rack
US6393483B1 (en) 1997-06-30 2002-05-21 Adaptec, Inc. Method and apparatus for network interface card load balancing and port aggregation
US7133940B2 (en) 1997-10-14 2006-11-07 Alacritech, Inc. Network interface device employing a DMA command queue
US6434620B1 (en) 1998-08-27 2002-08-13 Alacritech, Inc. TCP/IP offload network interface device
US6082845A (en) * 1998-05-29 2000-07-04 Lucent Technologies, Inc. Tiltable electronics cabinet
AU4334099A (en) * 1998-06-05 1999-12-20 Mylex Corporation Apparatus, system and method for n-way raid controller
US6223271B1 (en) * 1998-07-15 2001-04-24 Compaq Computer Corp. System and method for detecting system memory size using ROM based paging tables
US7664883B2 (en) * 1998-08-28 2010-02-16 Alacritech, Inc. Network interface device that fast-path processes solicited session layer read commands
US6714549B1 (en) * 1998-12-23 2004-03-30 Worldcom, Inc. High resiliency network infrastructure
US6356951B1 (en) 1999-03-01 2002-03-12 Sun Microsystems, Inc. System for parsing a packet for conformity with a predetermined protocol using mask and comparison values included in a parsing instruction
US6493756B1 (en) * 1999-10-28 2002-12-10 Networks Associates, Inc. System and method for dynamically sensing an asynchronous network event within a modular framework for network event processing
US6484224B1 (en) 1999-11-29 2002-11-19 Cisco Technology Inc. Multi-interface symmetric multiprocessor
US6816963B1 (en) * 2000-01-31 2004-11-09 Intel Corporation Platform level initialization using an image generated automatically by a remote server based upon description automatically generated and transmitted thereto by a processor-based system
US6990685B1 (en) * 2000-06-15 2006-01-24 Dell Products L.P. System and method for tracking bootable devices
US6459571B1 (en) * 2000-06-15 2002-10-01 Bull Hn Information Systems Inc. Packaging system for mass memory units
US20020064164A1 (en) * 2000-10-06 2002-05-30 Barany Peter A. Protocol header construction and/or removal for messages in wireless communications
US6498716B1 (en) * 2001-08-21 2002-12-24 Compaq Information Technologies Group, L.P. DC main power distribution
EP1446994A4 (de) * 2001-10-30 2006-05-17 Egenera Inc Vereinfachter stromversorgungs- und datenverbinder zur verwendung mit einem chassis-system, in dem mehrere prozessoren untergebracht sind
US6968414B2 (en) * 2001-12-04 2005-11-22 International Business Machines Corporation Monitoring insertion/removal of server blades in a data processing system
US6657867B2 (en) * 2001-12-14 2003-12-02 Hewlett-Packard Development Company, Lp. Hinged door for access to add-in cards
US20030172205A1 (en) * 2002-01-11 2003-09-11 Bastian Richard Henry Methods and components for mechanical computer
US7100031B1 (en) * 2002-03-27 2006-08-29 Hewlett-Packard Development Company, L.P. Detector and operational method for a firmware interface
US7257105B2 (en) * 2002-10-03 2007-08-14 Cisco Technology, Inc. L2 method for a wireless station to locate and associate with a wireless network in communication with a Mobile IP agent
WO2004092951A2 (en) * 2003-04-18 2004-10-28 Sap Ag Managing a computer system with blades
US20040249932A1 (en) * 2003-06-05 2004-12-09 Bunz Shain W. System and method for generating event notifications
US7467417B2 (en) * 2003-06-18 2008-12-16 Architecture Technology Corporation Active verification of boot firmware
US7864806B2 (en) 2004-01-06 2011-01-04 Broadcom Corp. Method and system for transmission control packet (TCP) segmentation offload
US7120778B2 (en) * 2004-02-18 2006-10-10 Intel Corporation Option ROM virtualization
US9264384B1 (en) * 2004-07-22 2016-02-16 Oracle International Corporation Resource virtualization mechanism including virtual host bus adapters
EP1630657A1 (de) * 2004-08-30 2006-03-01 STMicroelectronics S.r.l. Eingebetteter Speicher mit integrierter Datenverwaltung und Speichersystem dazu
US7469241B2 (en) * 2004-11-30 2008-12-23 Oracle International Corporation Efficient data aggregation operations using hash tables
US7386758B2 (en) * 2005-01-13 2008-06-10 Hitachi, Ltd. Method and apparatus for reconstructing data in object-based storage arrays
US7500573B1 (en) * 2005-01-21 2009-03-10 Flynn James T Saddle rack and harness rack lift
CN1809054A (zh) * 2005-01-21 2006-07-26 华为技术有限公司 基于会话初始协议的消息文本解码器
US7562366B2 (en) 2005-02-03 2009-07-14 Solarflare Communications, Inc. Transmit completion event batching
US7330965B2 (en) * 2005-02-09 2008-02-12 International Business Machines Corporation Multi-tiered boot list
US7577151B2 (en) * 2005-04-01 2009-08-18 International Business Machines Corporation Method and apparatus for providing a network connection table
US7574623B1 (en) * 2005-04-29 2009-08-11 Network Appliance, Inc. Method and system for rapidly recovering data from a “sick” disk in a RAID disk group
US7460758B2 (en) * 2005-06-03 2008-12-02 Telect Inc. Fiber management system
US7584347B2 (en) * 2005-06-10 2009-09-01 Dell Products L.P. System and method for identifying bootable device by generating a signature for each bootable device where the signature is independent of a location of the bootable device
US8713180B2 (en) * 2005-06-22 2014-04-29 Cisco Technology, Inc. Zero-copy network and file offload for web and application servers
US7791890B2 (en) * 2005-10-07 2010-09-07 Nec Corporation Computer system
JP2007133807A (ja) * 2005-11-14 2007-05-31 Hitachi Ltd データ処理システム、ストレージ装置及び管理装置
US7423870B2 (en) * 2005-11-18 2008-09-09 International Business Machines Corporation Blade server assembly
US7500073B1 (en) * 2006-03-29 2009-03-03 Sun Microsystems, Inc. Relocation of virtual-to-physical mappings
US20070233928A1 (en) * 2006-03-31 2007-10-04 Robert Gough Mechanism and apparatus for dynamically providing required resources for a hot-added PCI express endpoint or hierarchy
US7747749B1 (en) * 2006-05-05 2010-06-29 Google Inc. Systems and methods of efficiently preloading documents to client devices
US20080002711A1 (en) * 2006-06-30 2008-01-03 Bugenhagen Michael K System and method for access state based service options
US7987438B2 (en) * 2006-08-10 2011-07-26 International Business Machines Corporation Structure for initializing expansion adapters installed in a computer system having similar expansion adapters
JP4949804B2 (ja) * 2006-11-07 2012-06-13 株式会社日立製作所 統合管理計算機と記憶装置管理方法および計算機システム
JP4723470B2 (ja) * 2006-12-28 2011-07-13 株式会社日立製作所 計算機システムおよびそのチップセット
US8464024B2 (en) * 2007-04-27 2013-06-11 Hewlett-Packard Development Company, L.P. Virtual address hashing
US8644151B2 (en) * 2007-05-22 2014-02-04 Cisco Technology, Inc. Processing packet flows
CN101330446B (zh) * 2007-06-21 2012-05-09 中兴通讯股份有限公司 增强专用传输信道的帧协议层帧的解析方法
US7724668B2 (en) * 2007-06-27 2010-05-25 Verizon Patent And Licensing Inc. Bandwidth-based admission control mechanism
US7793071B2 (en) 2007-06-28 2010-09-07 Intel Corporation Method and system for reducing cache conflicts
US8151081B2 (en) * 2007-12-20 2012-04-03 Intel Corporation Method, system and apparatus for memory address mapping for sub-socket partitioning
FI123966B (fi) * 2008-02-04 2014-01-15 Tellabs Oy Tietoliikennelaite
US8610727B1 (en) * 2008-03-14 2013-12-17 Marvell International Ltd. Dynamic processing core selection for pre- and post-processing of multimedia workloads
US7801046B2 (en) 2008-04-28 2010-09-21 Oracle America, Inc. Method and system for bandwidth control on a network interface card
US9015444B2 (en) * 2008-06-09 2015-04-21 Panasonic Intellectual Property Management Co., Ltd. Access apparatus and available storage space calculation method
US8086838B2 (en) * 2008-08-13 2011-12-27 Dell Products L.P. Methods and systems for providing manufacturing mode detection and functionality in a UEFI BIOS
US8230442B2 (en) * 2008-09-05 2012-07-24 International Business Machines Corporation Executing an accelerator application program in a hybrid computing environment
US7921230B2 (en) * 2008-09-08 2011-04-05 International Business Corporation USB devices pre-configuration for KVM switch
US20100061207A1 (en) * 2008-09-09 2010-03-11 Seagate Technology Llc Data storage device including self-test features
TWI378384B (en) * 2008-10-15 2012-12-01 Phison Electronics Corp Mother board system, storage device for booting up thereof and connector
US8024719B2 (en) * 2008-11-03 2011-09-20 Advanced Micro Devices, Inc. Bounded hash table sorting in a dynamic program profiling system
DE112008004203B4 (de) 2008-12-25 2015-01-08 Mitsubishi Electric Corporation Kommunikationsverwaltungsvorrichtung, Kommnunikationsvorrichtung und Kommunikationsverfahren
US8112491B1 (en) 2009-01-16 2012-02-07 F5 Networks, Inc. Methods and systems for providing direct DMA
US8103809B1 (en) 2009-01-16 2012-01-24 F5 Networks, Inc. Network devices with multiple direct memory access channels and methods thereof
JP5393199B2 (ja) * 2009-03-02 2014-01-22 キヤノン株式会社 起動制御方法及び装置
US8266506B2 (en) * 2009-04-18 2012-09-11 Alcatel Lucent Method and apparatus for multiset membership testing using combinatorial bloom filters
WO2010140211A1 (ja) * 2009-06-01 2010-12-09 富士通株式会社 電子ユニット、電子システム及び収納装置
WO2011002437A1 (en) * 2009-06-29 2011-01-06 Hewlett-Packard Development Company, L.P. Memory agent to access memory blade as part of the cache coherency domain
US8910153B2 (en) * 2009-07-13 2014-12-09 Hewlett-Packard Development Company, L. P. Managing virtualized accelerators using admission control, load balancing and scheduling
US8275744B2 (en) * 2009-07-30 2012-09-25 Cleversafe, Inc. Dispersed storage network virtual address fields
US8832142B2 (en) * 2010-08-30 2014-09-09 Oracle International Corporation Query and exadata support for hybrid columnar compressed data
US9298662B2 (en) * 2009-12-08 2016-03-29 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Providing expansion card settings
US8743877B2 (en) 2009-12-21 2014-06-03 Steven L. Pope Header processing engine
JP5292321B2 (ja) * 2010-01-13 2013-09-18 アラクサラネットワークス株式会社 通信装置
US8473567B2 (en) * 2010-03-29 2013-06-25 Intel Corporation Generating a packet including multiple operation codes
US9754266B2 (en) * 2010-04-21 2017-09-05 Excalibur Ip, Llc Online serving threshold and delivery policy adjustment
US8504718B2 (en) * 2010-04-28 2013-08-06 Futurewei Technologies, Inc. System and method for a context layer switch
US9300576B2 (en) * 2010-05-03 2016-03-29 Pluribus Networks Inc. Methods, systems, and fabrics implementing a distributed network operating system
US8898324B2 (en) * 2010-06-24 2014-11-25 International Business Machines Corporation Data access management in a hybrid memory server
CN102141825B (zh) * 2010-07-09 2013-01-02 华为技术有限公司 机柜级服务器系统
US8909749B2 (en) * 2010-07-26 2014-12-09 International Business Macines Corporation Predictive context-based virtual workspace placement
TWI406624B (zh) * 2010-11-11 2013-08-21 Inventec Corp 伺服器
US10033585B2 (en) * 2010-12-15 2018-07-24 Juniper Networks, Inc. Methods and apparatus related to a switch fabric system having a multi-hop distributed control plane and a single-hop data plane
US8812746B2 (en) * 2010-12-16 2014-08-19 Intel Corporation Dynamically configurable device host controller
US8582299B1 (en) * 2010-12-23 2013-11-12 Amazon Technologies, Inc. System with movable computing devices
US8832674B2 (en) * 2011-02-24 2014-09-09 Software Ag Usa, Inc. Off-heap direct-memory data stores, methods of creating and/or managing off-heap direct-memory data stores, and/or systems including off-heap direct-memory data store
JP5422777B2 (ja) * 2011-03-07 2014-02-19 株式会社日立製作所 ネットワーク管理装置、ネットワーク管理方法及びネットワーク管理システム
US9405550B2 (en) * 2011-03-31 2016-08-02 International Business Machines Corporation Methods for the transmission of accelerator commands and corresponding command structure to remote hardware accelerator engines over an interconnect link
US9645628B1 (en) * 2011-05-09 2017-05-09 EMC IP Holding Company LLC Combined data storage and computing appliance that provides scalable storage in a clustered computing environment
US9042402B1 (en) * 2011-05-10 2015-05-26 Juniper Networks, Inc. Methods and apparatus for control protocol validation of a switch fabric system
GB201107860D0 (en) * 2011-05-11 2011-06-22 Manda Ion Rack module
US9369341B2 (en) * 2011-05-15 2016-06-14 Orbit Communication Systems Ltd. Static ring network for vehicle communications
JP6082389B2 (ja) * 2011-06-07 2017-02-15 シーゲイト テクノロジー エルエルシーＳｅａｇａｔｅ Ｔｅｃｈｎｏｌｏｇｙ ＬＬＣ ホストから見たデバイスファームウェア更新の影響の管理
US8812555B2 (en) * 2011-06-18 2014-08-19 Microsoft Corporation Dynamic lock-free hash tables
CN102902581B (zh) * 2011-07-29 2016-05-11 国际商业机器公司 硬件加速器及方法、中央处理单元、计算设备
CN102929360A (zh) * 2011-08-09 2013-02-13 鸿富锦精密工业（深圳）有限公司 服务器机柜
US8930307B2 (en) * 2011-09-30 2015-01-06 Pure Storage, Inc. Method for removing duplicate data from a storage array
US9021138B2 (en) * 2011-08-26 2015-04-28 Microsoft Technology Licensing, Llc Performance of multi-processor computer systems
CN102999139B (zh) * 2011-09-08 2016-03-30 英业达股份有限公司 供电装置与应用其的服务器机架系统
US8964601B2 (en) * 2011-10-07 2015-02-24 International Business Machines Corporation Network switching domains with a virtualized control plane
CN103139106B (zh) * 2011-11-28 2014-06-11 英业达科技有限公司 服务器机架系统
US8826277B2 (en) * 2011-11-29 2014-09-02 International Business Machines Corporation Cloud provisioning accelerator
US9342314B2 (en) * 2011-12-08 2016-05-17 Oracle International Corporation Efficient hardware instructions for single instruction multiple data processors
US8788663B1 (en) * 2011-12-20 2014-07-22 Amazon Technologies, Inc. Managing resource dependent workflows
CN106469029B (zh) * 2011-12-31 2019-07-23 华为数字技术（成都）有限公司 数据分层存储处理方法、装置和存储设备
US8708736B2 (en) * 2012-02-01 2014-04-29 Dell Products L.P. Systems and methods for coupling AC power to a rack-level power infrastructure
EP2831693B1 (de) * 2012-03-30 2018-06-13 Intel Corporation Vorrichtung und verfahren zur beschleunigung der operationen bei einem prozessor mit einem gemeinsam genutzten virtuellen speicher
EP2831721B1 (de) * 2012-03-30 2020-08-26 Intel Corporation Kontextumschaltungsmechanismus für einen prozessorkern mit einem universal-cpu-kern und einem fest gekoppelten beschleuniger
US8868868B1 (en) * 2012-05-31 2014-10-21 Netapp, Inc. Method and system for responding to client requests for information maintained by storage systems
US9613052B2 (en) * 2012-06-05 2017-04-04 International Business Machines Corporation Establishing trust within a cloud computing system
US9710762B2 (en) * 2012-06-06 2017-07-18 Juniper Networks, Inc. Dynamic logging
CN104272288B (zh) 2012-06-08 2018-01-30 英特尔公司 用于实现虚拟机vm平台通信回送的方法和系统
US8838577B2 (en) * 2012-07-24 2014-09-16 International Business Machines Corporation Accelerated row decompression
CN103634330A (zh) * 2012-08-20 2014-03-12 曙光信息产业(北京)有限公司 一种云计算环境下的资源自动分配方法
US9154298B2 (en) * 2012-08-31 2015-10-06 Cleversafe, Inc. Securely storing data in a dispersed storage network
US9049114B2 (en) * 2012-08-31 2015-06-02 Cisco Technology, Inc. Network access device and method for automatically establishing connection to a wide area network
US10230762B2 (en) * 2012-08-31 2019-03-12 Jpmorgan Chase Bank, N.A. System and method for sharing information in a private ecosystem
US10554505B2 (en) * 2012-09-28 2020-02-04 Intel Corporation Managing data center resources to achieve a quality of service
US8938417B2 (en) * 2013-02-22 2015-01-20 International Business Machines Corporation Integrity checking and selective deduplication based on network parameters
JP6009097B2 (ja) * 2013-02-27 2016-10-19 ヒタチ データ システムズ コーポレーションＨｉｔａｃｈｉ Ｄａｔａ Ｓｙｓｔｅｍｓ Ｃｏｒｐｏｒａｔｉｏｎ 分散オブジェクトストレージエコシステムにおけるコンテンツとメタデータの分離
US20140282584A1 (en) * 2013-03-14 2014-09-18 Silicon Graphics International Corp. Allocating Accelerators to Threads in a High Performance Computing System
US9558010B2 (en) * 2013-03-14 2017-01-31 International Business Machines Corporation Fast hot boot of a computer system
US9317444B2 (en) 2013-03-15 2016-04-19 Vmware, Inc. Latency reduction for direct memory access operations involving address translation
ES2719271T3 (es) * 2013-03-19 2019-07-09 Adc Czech Republic Sro Control de curvatura y soporte de cables de conexión, móviles, para paneles de telecomunicaciones
US9734100B2 (en) * 2013-03-21 2017-08-15 Insyde Software Corp. Network controller sharing between SMM firmware and OS drivers
US10037061B1 (en) * 2013-04-30 2018-07-31 Amazon Technologies, Inc. Multiple-stage cooling system for rack
US8898227B1 (en) * 2013-05-10 2014-11-25 Owl Computing Technologies, Inc. NFS storage via multiple one-way data links
US9424079B2 (en) * 2013-06-27 2016-08-23 Microsoft Technology Licensing, Llc Iteration support in a heterogeneous dataflow engine
US9056464B2 (en) * 2013-07-16 2015-06-16 Xerox Corporation System and method for optimized application of release agent in an inkjet printer with in-line coating
WO2015023537A2 (en) * 2013-08-16 2015-02-19 Interdigital Patent Holdings, Inc. Methods and apparatus for hash routing in software defined networking
US10684973B2 (en) 2013-08-30 2020-06-16 Intel Corporation NUMA node peripheral switch
US9444914B2 (en) * 2013-09-16 2016-09-13 Annapurna Labs Ltd. Configurable parser and a method for parsing information units
WO2015039687A1 (en) * 2013-09-19 2015-03-26 Huawei Technologies Co., Ltd. Transmission and reception devices for reducing the delay in end-to-end delivery of network packets
US9606921B2 (en) * 2013-09-21 2017-03-28 Oracle International Corporation Granular creation and refresh of columnar data
CN106537863B (zh) * 2013-10-17 2019-11-26 马维尔国际贸易有限公司 用于并发地处理网络分组的方法和设备
US9411601B2 (en) * 2013-10-29 2016-08-09 Intel Corporation Flexible bootstrap code architecture
JP6404347B2 (ja) * 2013-12-20 2018-10-10 インテル・コーポレーション 実行オフロード
WO2015109090A1 (en) * 2014-01-17 2015-07-23 F5 Networks, Inc. Systems and methods for network destination based flood attack mitigation
US9740714B2 (en) * 2014-02-06 2017-08-22 International Business Machines Corporation Multilevel filters for cache-efficient access
US20150293699A1 (en) * 2014-04-11 2015-10-15 Graham Bromley Network-attached storage enhancement appliance
CN106233673B (zh) * 2014-04-29 2019-07-19 慧与发展有限责任合伙企业 用于网络服务插入的设备和方法
US9356883B1 (en) * 2014-05-29 2016-05-31 Amazon Technologies, Inc. Allocating cloud-hosted application resources using end-user metrics
US9684575B2 (en) * 2014-06-23 2017-06-20 Liqid Inc. Failover handling in modular switched fabric for data storage systems
US9626108B2 (en) * 2014-09-16 2017-04-18 Kove Ip, Llc Dynamically provisionable and allocatable external memory
US10275171B2 (en) * 2014-09-16 2019-04-30 Kove Ip, Llc Paging of external memory
WO2016045055A1 (en) * 2014-09-25 2016-03-31 Intel Corporation Network communications using pooled memory in rack-scale architecture
US9971619B2 (en) * 2014-10-15 2018-05-15 Keysight Technologies Singapore (Holdings) Pte Ltd Methods and systems for forwarding network packets within virtual machine host systems
US9501420B2 (en) * 2014-10-22 2016-11-22 Netapp, Inc. Cache optimization technique for large working data sets
US9596253B2 (en) * 2014-10-30 2017-03-14 Splunk Inc. Capture triggers for capturing network data
US10116772B2 (en) 2014-11-14 2018-10-30 Cavium, Inc. Network switching with co-resident data-plane and network interface controllers
US10230824B2 (en) * 2014-11-17 2019-03-12 Keysight Technologies Singapore (Holdings) Pte. Lte. Packet classification using memory pointer information
US10394731B2 (en) * 2014-12-19 2019-08-27 Amazon Technologies, Inc. System on a chip comprising reconfigurable resources for multiple compute sub-systems
US9838333B2 (en) * 2015-01-20 2017-12-05 Futurewei Technologies, Inc. Software-defined information centric network (ICN)
US9560078B2 (en) * 2015-02-04 2017-01-31 Intel Corporation Technologies for scalable security architecture of virtualized networks
US9767856B2 (en) * 2015-02-10 2017-09-19 Netapp, Inc. High density storage device system
US10833940B2 (en) * 2015-03-09 2020-11-10 Vapor IO Inc. Autonomous distributed workload and infrastructure scheduling
US9569267B2 (en) * 2015-03-16 2017-02-14 Intel Corporation Hardware-based inter-device resource sharing
US9792154B2 (en) * 2015-04-17 2017-10-17 Microsoft Technology Licensing, Llc Data processing system having a hardware acceleration plane and a software plane
US10606651B2 (en) 2015-04-17 2020-03-31 Microsoft Technology Licensing, Llc Free form expression accelerator with thread length-based thread assignment to clustered soft processor cores that share a functional circuit
IL238690B (en) * 2015-05-07 2019-07-31 Mellanox Technologies Ltd Network-based computational accelerator
US9578008B2 (en) * 2015-05-11 2017-02-21 Intel Corporation Technologies for secure bootstrapping of virtual network functions
US9606836B2 (en) * 2015-06-09 2017-03-28 Microsoft Technology Licensing, Llc Independently networkable hardware accelerators for increased workflow optimization
US10049078B1 (en) * 2015-06-25 2018-08-14 Amazon Technologies, Inc. Accessing a memory location using a two-stage hash scheme
US10063446B2 (en) * 2015-06-26 2018-08-28 Intel Corporation Netflow collection and export offload using network silicon
US9668382B2 (en) * 2015-08-11 2017-05-30 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Coolant distribution unit for a multi-node chassis
US9891935B2 (en) * 2015-08-13 2018-02-13 Altera Corporation Application-based dynamic heterogeneous many-core systems and methods
US9749266B2 (en) * 2015-08-28 2017-08-29 International Business Machines Corporation Coalescing messages using a network interface controller
US10296232B2 (en) * 2015-09-01 2019-05-21 Western Digital Technologies, Inc. Service level based control of storage systems
CN105183561B (zh) * 2015-09-02 2018-09-14 浪潮(北京)电子信息产业有限公司 一种资源分配方法和系统
US11068469B2 (en) * 2015-09-04 2021-07-20 Arista Networks, Inc. System and method of a dynamic shared memory hash table with notifications
US10321597B2 (en) * 2015-09-07 2019-06-11 Dell Products, L.P. User interface enhanced storage sled handle with embedded security features
US10725963B2 (en) * 2015-09-12 2020-07-28 Microsoft Technology Licensing, Llc Distributed lock-free RDMA-based memory allocation and de-allocation
US20170093770A1 (en) * 2015-09-25 2017-03-30 Intel Corporation Technologies for receive side message inspection and filtering
US10320710B2 (en) * 2015-09-25 2019-06-11 Intel Corporation Reliable replication mechanisms based on active-passive HFI protocols built on top of non-reliable multicast fabric implementations
WO2017052575A1 (en) * 2015-09-25 2017-03-30 Intel Corporation Extending multichip package link off package
CN105357258B (zh) * 2015-09-28 2020-06-26 华为技术有限公司 一种加速管理节点、加速节点、客户端及方法
US9996539B1 (en) * 2015-09-30 2018-06-12 EMC IP Holding Company LLC Data protection and long term retention
US9959146B2 (en) * 2015-10-20 2018-05-01 Intel Corporation Computing resources workload scheduling
US9912788B2 (en) * 2015-11-10 2018-03-06 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods of an enhanced state-aware proxy device
US10206297B2 (en) * 2015-11-23 2019-02-12 Liqid Inc. Meshed architecture rackmount storage assembly
US10691731B2 (en) * 2015-11-26 2020-06-23 International Business Machines Corporation Efficient lookup in multiple bloom filters
US10713175B2 (en) * 2015-12-02 2020-07-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and memory availability managing module for managing availability of memory pages
US10218647B2 (en) * 2015-12-07 2019-02-26 Intel Corporation Mechanism to support multiple-writer/multiple-reader concurrency for software flow/packet classification on general purpose multi-core systems
KR102509988B1 (ko) * 2015-12-15 2023-03-14 삼성전자주식회사 커넥션 기반 로드 밸런싱을 위한 저장 시스템 및 방법
US10230633B2 (en) * 2016-01-21 2019-03-12 Red Hat, Inc. Shared memory communication in software defined networking
CN108369520B (zh) * 2016-01-25 2022-03-08 惠普发展公司，有限责任合伙企业 保护基本输入/输出(bios)代码
US10713314B2 (en) * 2016-01-29 2020-07-14 Splunk Inc. Facilitating data model acceleration in association with an external data system
KR101936950B1 (ko) * 2016-02-15 2019-01-11 주식회사 맴레이 컴퓨팅 디바이스, 코프로세서와 비휘발성 메모리 사이의 데이터 이동 방법 및 이를 포함하는 프로그램
US9933821B2 (en) * 2016-02-17 2018-04-03 Quanta Computer Inc. Chassis with lock mechanism
US10180992B2 (en) * 2016-03-01 2019-01-15 Microsoft Technology Licensing, Llc Atomic updating of graph database index structures
US20170257970A1 (en) * 2016-03-04 2017-09-07 Radisys Corporation Rack having uniform bays and an optical interconnect system for shelf-level, modular deployment of sleds enclosing information technology equipment
US10069688B2 (en) * 2016-03-07 2018-09-04 International Business Machines Corporation Dynamically assigning, by functional domain, separate pairs of servers to primary and backup service processor modes within a grouping of servers
US10248349B2 (en) * 2016-03-22 2019-04-02 Oracle International Corporation Efficient and thread-safe objects for dynamically-typed languages
US10146550B2 (en) * 2016-03-28 2018-12-04 Dell Products, L.P. System and method to remotely detect and report bootable physical disk location
US10523598B2 (en) * 2016-04-04 2019-12-31 Futurewei Technologies, Inc. Multi-path virtual switching
US20180024964A1 (en) * 2016-07-19 2018-01-25 Pure Storage, Inc. Disaggregated compute resources and storage resources in a storage system
US10034407B2 (en) * 2016-07-22 2018-07-24 Intel Corporation Storage sled for a data center
US10873521B2 (en) 2016-07-22 2020-12-22 Intel Corporation Methods and apparatus for SDI support for fast startup
US10917456B2 (en) * 2016-07-25 2021-02-09 Red Hat, Inc. Application management in an application deployment pipeline
US10078468B2 (en) * 2016-08-18 2018-09-18 International Business Machines Corporation Slice migration in a dispersed storage network
US10277677B2 (en) * 2016-09-12 2019-04-30 Intel Corporation Mechanism for disaggregated storage class memory over fabric
US20180089044A1 (en) * 2016-09-27 2018-03-29 Francesc Guim Bernat Technologies for providing network interface support for remote memory and storage failover protection
US10853364B2 (en) * 2016-09-28 2020-12-01 Microsoft Technology Licensing, Llc Direct table association in in-memory databases
US10936533B2 (en) 2016-10-18 2021-03-02 Advanced Micro Devices, Inc. GPU remote communication with triggered operations
US20180150256A1 (en) * 2016-11-29 2018-05-31 Intel Corporation Technologies for data deduplication in disaggregated architectures
KR20190086669A (ko) * 2016-12-12 2019-07-23 인텔 코포레이션 프로세서 아키텍처에 대한 장치들 및 방법들
US10171309B1 (en) * 2016-12-23 2019-01-01 EMC IP Holding Company LLC Topology service
US10824355B2 (en) * 2017-01-10 2020-11-03 International Business Machines Corporation Hierarchical management of storage capacity and data volumes in a converged system
US10198270B2 (en) * 2017-01-19 2019-02-05 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Dynamic hardware configuration via firmware interface at computing device boot
US20180212885A1 (en) 2017-01-20 2018-07-26 Google Inc. Device and method for scalable traffic shaping at a receiver with a time-indexed data structure
US10922296B2 (en) * 2017-03-01 2021-02-16 Sap Se In-memory row storage durability
US10503427B2 (en) * 2017-03-10 2019-12-10 Pure Storage, Inc. Synchronously replicating datasets and other managed objects to cloud-based storage systems
US10628057B2 (en) * 2017-03-28 2020-04-21 Hewlett Packard Enterprise Development Lp Capability based locking and access of shared persistent memory
US10346315B2 (en) * 2017-05-26 2019-07-09 Oracle International Corporation Latchless, non-blocking dynamically resizable segmented hash index
US10324859B2 (en) * 2017-06-26 2019-06-18 Western Digital Technologies, Inc. Multi-plane memory management
US20190044809A1 (en) * 2017-08-30 2019-02-07 Intel Corporation Technologies for managing a flexible host interface of a network interface controller
US10334760B1 (en) * 2018-01-12 2019-06-25 Jed A. Darland System and method for helical cooling tower for efficient cooling
US10447273B1 (en) * 2018-09-11 2019-10-15 Advanced Micro Devices, Inc. Dynamic virtualized field-programmable gate array resource control for performance and reliability

Cited By (100)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11128553B2 (en) 2016-07-22 2021-09-21 Intel Corporation Technologies for switching network traffic in a data center
US10785549B2 (en) 2016-07-22 2020-09-22 Intel Corporation Technologies for switching network traffic in a data center
US10791384B2 (en) 2016-07-22 2020-09-29 Intel Corporation Technologies for switching network traffic in a data center
US10802229B2 (en) 2016-07-22 2020-10-13 Intel Corporation Technologies for switching network traffic in a data center
US12040889B2 (en) 2016-07-22 2024-07-16 Intel Corporation Technologies for switching network traffic in a data center
US12081323B2 (en) 2016-07-22 2024-09-03 Intel Corporation Techniques to control system updates and configuration changes via the cloud
US11595277B2 (en) 2016-07-22 2023-02-28 Intel Corporation Technologies for switching network traffic in a data center
US11907557B2 (en) 2016-11-29 2024-02-20 Intel Corporation Technologies for dividing work across accelerator devices
US11995330B2 (en) 2016-11-29 2024-05-28 Intel Corporation Technologies for providing accelerated functions as a service in a disaggregated architecture
US11977923B2 (en) 2016-11-29 2024-05-07 Intel Corporation Cloud-based scale-up system composition
US11137922B2 (en) 2016-11-29 2021-10-05 Intel Corporation Technologies for providing accelerated functions as a service in a disaggregated architecture
US10911358B1 (en) * 2017-09-26 2021-02-02 Amazon Technologies, Inc. Packet processing cache
US11444890B2 (en) * 2018-01-28 2022-09-13 Drivenets Ltd. Method and device for improving bandwidth utilization in a communication network
US11182322B2 (en) 2018-09-25 2021-11-23 International Business Machines Corporation Efficient component communication through resource rewiring in disaggregated datacenters
US20200097427A1 (en) * 2018-09-25 2020-03-26 International Business Machines Corporation Efficient component communication through protocol switching in disaggregated datacenters
US11163713B2 (en) * 2018-09-25 2021-11-02 International Business Machines Corporation Efficient component communication through protocol switching in disaggregated datacenters
US10802988B2 (en) 2018-09-25 2020-10-13 International Business Machines Corporation Dynamic memory-based communication in disaggregated datacenters
US11650849B2 (en) 2018-09-25 2023-05-16 International Business Machines Corporation Efficient component communication through accelerator switching in disaggregated datacenters
US11012423B2 (en) 2018-09-25 2021-05-18 International Business Machines Corporation Maximizing resource utilization through efficient component communication in disaggregated datacenters
US10831698B2 (en) 2018-09-25 2020-11-10 International Business Machines Corporation Maximizing high link bandwidth utilization through efficient component communication in disaggregated datacenters
US10915493B2 (en) 2018-09-25 2021-02-09 International Business Machines Corporation Component building blocks and optimized compositions thereof in disaggregated datacenters
US10983985B2 (en) * 2018-10-29 2021-04-20 International Business Machines Corporation Determining a storage pool to store changed data objects indicated in a database
US11023155B2 (en) 2018-10-29 2021-06-01 International Business Machines Corporation Processing event messages for changed data objects to determine a storage pool to store the changed data objects
US11409900B2 (en) 2018-11-15 2022-08-09 International Business Machines Corporation Processing event messages for data objects in a message queue to determine data to redact
US11429674B2 (en) 2018-11-15 2022-08-30 International Business Machines Corporation Processing event messages for data objects to determine data to redact from a database
US11818058B2 (en) 2019-04-26 2023-11-14 Intel Corporation Shared resources for multiple communication traffics
US11088967B2 (en) * 2019-04-26 2021-08-10 Intel Corporation Shared resources for multiple communication traffics
US11376934B2 (en) 2019-05-20 2022-07-05 Mountain Top Industries Aps Lid arrangement for a canister for a rollup truck bed cover
US12034633B2 (en) 2019-05-23 2024-07-09 Hewlett Packard Enterprise Development Lp System and method for facilitating tracer packets in a data-driven intelligent network
US11792114B2 (en) 2019-05-23 2023-10-17 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient management of non-idempotent operations in a network interface controller (NIC)
US12040969B2 (en) 2019-05-23 2024-07-16 Hewlett Packard Enterprise Development Lp System and method for facilitating data-driven intelligent network with flow control of individual applications and traffic flows
US12058033B2 (en) 2019-05-23 2024-08-06 Hewlett Packard Enterprise Development Lp Method and system for providing network ingress fairness between applications
US11882025B2 (en) 2019-05-23 2024-01-23 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient message matching in a network interface controller (NIC)
US12021738B2 (en) 2019-05-23 2024-06-25 Hewlett Packard Enterprise Development Lp Deadlock-free multicast routing on a dragonfly network
US12003411B2 (en) 2019-05-23 2024-06-04 Hewlett Packard Enterprise Development Lp Systems and methods for on the fly routing in the presence of errors
US20220210058A1 (en) * 2019-05-23 2022-06-30 Hewlett Packard Enterprise Development Lp Fat tree adaptive routing
US20220197845A1 (en) * 2019-05-23 2022-06-23 Hewlett Packard Enterprise Development Lp System and method for facilitating operation management in a network interface controller (nic) for accelerators
US11991072B2 (en) 2019-05-23 2024-05-21 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient event notification management for a network interface controller (NIC)
US11985060B2 (en) 2019-05-23 2024-05-14 Hewlett Packard Enterprise Development Lp Dragonfly routing with incomplete group connectivity
US20220197831A1 (en) * 2019-05-23 2022-06-23 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient host memory access from a network interface controller (nic)
US11973685B2 (en) * 2019-05-23 2024-04-30 Hewlett Packard Enterprise Development Lp Fat tree adaptive routing
US11750504B2 (en) 2019-05-23 2023-09-05 Hewlett Packard Enterprise Development Lp Method and system for providing network egress fairness between applications
US11757763B2 (en) * 2019-05-23 2023-09-12 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient host memory access from a network interface controller (NIC)
US11757764B2 (en) 2019-05-23 2023-09-12 Hewlett Packard Enterprise Development Lp Optimized adaptive routing to reduce number of hops
US11765074B2 (en) 2019-05-23 2023-09-19 Hewlett Packard Enterprise Development Lp System and method for facilitating hybrid message matching in a network interface controller (NIC)
US11777843B2 (en) 2019-05-23 2023-10-03 Hewlett Packard Enterprise Development Lp System and method for facilitating data-driven intelligent network
US11784920B2 (en) 2019-05-23 2023-10-10 Hewlett Packard Enterprise Development Lp Algorithms for use of load information from neighboring nodes in adaptive routing
US12058032B2 (en) 2019-05-23 2024-08-06 Hewlett Packard Enterprise Development Lp Weighting routing
US11968116B2 (en) 2019-05-23 2024-04-23 Hewlett Packard Enterprise Development Lp Method and system for facilitating lossy dropping and ECN marking
US11799764B2 (en) 2019-05-23 2023-10-24 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient packet injection into an output buffer in a network interface controller (NIC)
US11962490B2 (en) 2019-05-23 2024-04-16 Hewlett Packard Enterprise Development Lp Systems and methods for per traffic class routing
US12132648B2 (en) 2019-05-23 2024-10-29 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient load balancing in a network interface controller (NIC)
US11818037B2 (en) 2019-05-23 2023-11-14 Hewlett Packard Enterprise Development Lp Switch device for facilitating switching in data-driven intelligent network
US11929919B2 (en) 2019-05-23 2024-03-12 Hewlett Packard Enterprise Development Lp System and method for facilitating self-managing reduction engines
US11916781B2 (en) 2019-05-23 2024-02-27 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient utilization of an output buffer in a network interface controller (NIC)
US11899596B2 (en) 2019-05-23 2024-02-13 Hewlett Packard Enterprise Development Lp System and method for facilitating dynamic command management in a network interface controller (NIC)
US11848859B2 (en) 2019-05-23 2023-12-19 Hewlett Packard Enterprise Development Lp System and method for facilitating on-demand paging in a network interface controller (NIC)
US11855881B2 (en) 2019-05-23 2023-12-26 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient packet forwarding using a message state table in a network interface controller (NIC)
US11916782B2 (en) 2019-05-23 2024-02-27 Hewlett Packard Enterprise Development Lp System and method for facilitating global fairness in a network
US11863431B2 (en) 2019-05-23 2024-01-02 Hewlett Packard Enterprise Development Lp System and method for facilitating fine-grain flow control in a network interface controller (NIC)
WO2020236274A1 (en) * 2019-05-23 2020-11-26 Cray Inc. System and method for facilitating efficient event notification management for a network interface controller (nic)
US11902150B2 (en) 2019-05-23 2024-02-13 Hewlett Packard Enterprise Development Lp Systems and methods for adaptive routing in the presence of persistent flows
US11876701B2 (en) * 2019-05-23 2024-01-16 Hewlett Packard Enterprise Development Lp System and method for facilitating operation management in a network interface controller (NIC) for accelerators
US11876702B2 (en) 2019-05-23 2024-01-16 Hewlett Packard Enterprise Development Lp System and method for facilitating efficient address translation in a network interface controller (NIC)
US11831869B2 (en) 2019-07-09 2023-11-28 Beijing Bytedance Network Technology Co., Ltd. Sample determination for adaptive loop filtering
JP2022539845A (ja) * 2019-07-11 2022-09-13 北京字節跳動網絡技術有限公司 適応ループフィルタリングにおけるサンプルパディング
JP7549081B2 (ja) 2019-07-11 2024-09-10 北京字節跳動網絡技術有限公司 適応ループフィルタリングにおけるサンプルパディング
JP7291845B2 (ja) 2019-07-11 2023-06-15 北京字節跳動網絡技術有限公司 適応ループフィルタリングにおけるサンプルパディング
US12120297B2 (en) 2019-07-11 2024-10-15 Beijing Bytedance Network Technology Co., Ltd. Sample padding in adaptive loop filtering
US11483246B2 (en) 2020-01-13 2022-10-25 Vmware, Inc. Tenant-specific quality of service
US12120032B2 (en) 2020-01-13 2024-10-15 VMware LLC Tenant-specific quality of service
US11599395B2 (en) * 2020-02-19 2023-03-07 Vmware, Inc. Dynamic core allocation
US11962518B2 (en) 2020-06-02 2024-04-16 VMware LLC Hardware acceleration techniques using flow selection
US11539633B2 (en) 2020-08-31 2022-12-27 Vmware, Inc. Determining whether to rate limit traffic
US12095668B2 (en) 2020-08-31 2024-09-17 VMware LLC Determining whether to rate limit traffic
TWI797627B (zh) * 2020-09-16 2023-04-01 日商鎧俠股份有限公司 通訊系統、記憶體元件及通訊方法
US11606310B2 (en) * 2020-09-28 2023-03-14 Vmware, Inc. Flow processing offload using virtual port identifiers
US20220103478A1 (en) * 2020-09-28 2022-03-31 Vmware, Inc. Flow processing offload using virtual port identifiers
US11636053B2 (en) 2020-09-28 2023-04-25 Vmware, Inc. Emulating a local storage by accessing an external storage through a shared port of a NIC
US11736566B2 (en) 2020-09-28 2023-08-22 Vmware, Inc. Using a NIC as a network accelerator to allow VM access to an external storage via a PF module, bus, and VF module
US11736565B2 (en) 2020-09-28 2023-08-22 Vmware, Inc. Accessing an external storage through a NIC
US11716383B2 (en) 2020-09-28 2023-08-01 Vmware, Inc. Accessing multiple external storages to present an emulated local storage through a NIC
US11829793B2 (en) 2020-09-28 2023-11-28 Vmware, Inc. Unified management of virtual machines and bare metal computers
US11875172B2 (en) 2020-09-28 2024-01-16 VMware LLC Bare metal computer for booting copies of VM images on multiple computing devices using a smart NIC
US11792134B2 (en) 2020-09-28 2023-10-17 Vmware, Inc. Configuring PNIC to perform flow processing offload using virtual port identifiers
US11593278B2 (en) 2020-09-28 2023-02-28 Vmware, Inc. Using machine executing on a NIC to access a third party storage not supported by a NIC or host
US11824931B2 (en) 2020-09-28 2023-11-21 Vmware, Inc. Using physical and virtual functions associated with a NIC to access an external storage through network fabric driver
US12021759B2 (en) 2020-09-28 2024-06-25 VMware LLC Packet processing with hardware offload units
EP4283468A4 (de) * 2021-03-11 2024-07-10 Huawei Tech Co Ltd Datenübertragungssystem und zugehörige vorrichtung
US11799784B2 (en) 2021-06-08 2023-10-24 Vmware, Inc. Virtualized QoS support in software defined networks
US11871547B2 (en) 2021-09-02 2024-01-09 Baidu Usa Llc Two phase system for enclosure systems
US11910575B2 (en) * 2021-09-02 2024-02-20 Baidu Usa Llc Rack systems and packaging for servers
US20230067118A1 (en) * 2021-09-02 2023-03-02 Baidu Usa Llc Rack systems and packaging for servers
US11995024B2 (en) 2021-12-22 2024-05-28 VMware LLC State sharing between smart NICs
US11863376B2 (en) 2021-12-22 2024-01-02 Vmware, Inc. Smart NIC leader election
US20230214337A1 (en) * 2022-01-06 2023-07-06 Vmware, Inc. Methods and systems for extablishing direct communications between a server computer and a smart network interface controller
US11928367B2 (en) 2022-06-21 2024-03-12 VMware LLC Logical memory addressing for network devices
US11928062B2 (en) 2022-06-21 2024-03-12 VMware LLC Accelerating data message classification with smart NICs
US11899594B2 (en) 2022-06-21 2024-02-13 VMware LLC Maintenance of data message classification cache on smart NIC
US20240020357A1 (en) * 2022-07-15 2024-01-18 Vmware, Inc. Keyless licensing in a multi-cloud computing system

Also Published As

Publication number Publication date
US20220012105A1 (en) 2022-01-13
CN109426455A (zh) 2019-03-05
US20190044859A1 (en) 2019-02-07
CN109426647B (zh) 2024-10-29
US20240195605A1 (en) 2024-06-13
US20190044849A1 (en) 2019-02-07
US20190034102A1 (en) 2019-01-31
US20210306142A1 (en) 2021-09-30
CN117725004A (zh) 2024-03-19
US10581596B2 (en) 2020-03-03
US20190042090A1 (en) 2019-02-07
EP3451635A1 (de) 2019-03-06
US10554391B2 (en) 2020-02-04
US20190042277A1 (en) 2019-02-07
US20190042126A1 (en) 2019-02-07
CN113806260A (zh) 2021-12-17
EP3451635B1 (de) 2020-07-15
CN109426649A (zh) 2019-03-05
US20190034383A1 (en) 2019-01-31
US20230412365A1 (en) 2023-12-21
CN112732447B (zh) 2024-05-14
US20190035483A1 (en) 2019-01-31
US11025411B2 (en) 2021-06-01
US20190042234A1 (en) 2019-02-07
US11050554B2 (en) 2021-06-29
US20190034490A1 (en) 2019-01-31
EP3454530A1 (de) 2019-03-13
US10469252B2 (en) 2019-11-05
CN109426648B (zh) 2024-09-10
US20190042091A1 (en) 2019-02-07
US11588624B2 (en) 2023-02-21
CN109426648A (zh) 2019-03-05
US10567166B2 (en) 2020-02-18
US20210288793A1 (en) 2021-09-16
CN109428770B (zh) 2024-08-13
US10756886B2 (en) 2020-08-25
US11522682B2 (en) 2022-12-06
US20190052457A1 (en) 2019-02-14
US11888967B2 (en) 2024-01-30
US20190069434A1 (en) 2019-02-28
EP3451196A1 (de) 2019-03-06
US20230421358A1 (en) 2023-12-28
US10476670B2 (en) 2019-11-12
EP3823245A1 (de) 2021-05-19
CN109428770A (zh) 2019-03-05
JP7214394B2 (ja) 2023-01-30
CN109426647A (zh) 2019-03-05
CN109426569A (zh) 2019-03-05
CN113806260B (zh) 2024-10-15
EP3460662A1 (de) 2019-03-27
CN112732447A (zh) 2021-04-30
CN115543204A (zh) 2022-12-30
US20230050698A1 (en) 2023-02-16
CN109426652A (zh) 2019-03-05
US20190042122A1 (en) 2019-02-07
US10728024B2 (en) 2020-07-28
US20200389296A1 (en) 2020-12-10
DE102018212479A1 (de) 2019-02-28
JP2019047489A (ja) 2019-03-22
CN116501683A (zh) 2023-07-28
US20190042611A1 (en) 2019-02-07
US11843691B2 (en) 2023-12-12
CN109426456A (zh) 2019-03-05
US20190042136A1 (en) 2019-02-07
CN109426649B (zh) 2024-09-03
US11249816B2 (en) 2022-02-15
US20190042408A1 (en) 2019-02-07

Similar Documents

Publication Publication Date Title
US11843691B2 (en) Technologies for managing a flexible host interface of a network interface controller
US10732879B2 (en) Technologies for processing network packets by an intelligent network interface controller
US11467885B2 (en) Technologies for managing a latency-efficient pipeline through a network interface controller
US11630702B2 (en) Cloud-based scale-up system composition
EP3716088B1 (de) Technologien zur flexiblen protokollbeschleunigung

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTEL CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WILLIS, THOMAS E.;BURRES, BRAD;KUMAR, AMIT;SIGNING DATES FROM 20180117 TO 20180503;REEL/FRAME:045730/0022

STCT Information on status: administrative procedure adjustment

Free format text: PROSECUTION SUSPENDED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION