[go: up one dir, main page]

US20120284501A1 - Computing system with hardware reconfiguration mechanism and method of operation thereof - Google Patents

Computing system with hardware reconfiguration mechanism and method of operation thereof Download PDF

Info

Publication number
US20120284501A1
US20120284501A1 US13/464,627 US201213464627A US2012284501A1 US 20120284501 A1 US20120284501 A1 US 20120284501A1 US 201213464627 A US201213464627 A US 201213464627A US 2012284501 A1 US2012284501 A1 US 2012284501A1
Authority
US
United States
Prior art keywords
cluster
application
bitstream
module
reconfigurable hardware
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
US13/464,627
Other languages
English (en)
Inventor
Peter J. Zievers
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.)
XCELEMOR Inc
Original Assignee
XCELEMOR Inc
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 XCELEMOR Inc filed Critical XCELEMOR Inc
Priority to US13/464,627 priority Critical patent/US20120284501A1/en
Assigned to XCELEMOR, INC. reassignment XCELEMOR, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ZIEVERS, PETER J.
Publication of US20120284501A1 publication Critical patent/US20120284501A1/en
Priority to US16/297,431 priority patent/US11494322B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06F13/1689—Synchronisation and timing concerns
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06F13/1694—Configuration of memory controller to different memory types
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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 OR CALCULATING; 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/7803—System on board, i.e. computer system on one or more PCB, e.g. motherboards, daughterboards or blades
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/7807—System on chip, i.e. computer system on a single chip; System in package, i.e. computer system on one or more chips in a single package
    • G06F15/781—On-chip cache; Off-chip memory
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/30—Circuit design
    • G06F30/32—Circuit design at the digital level
    • G06F30/33—Design verification, e.g. functional simulation or model checking
    • G06F30/3308—Design verification, e.g. functional simulation or model checking using simulation
    • G06F30/331—Design verification, e.g. functional simulation or model checking using simulation with hardware acceleration, e.g. by using field programmable gate array [FPGA] or emulation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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]
    • G06F30/347—Physical level, e.g. placement or routing
    • 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/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • 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/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/10—Packet switching elements characterised by the switching fabric construction
    • H04L49/111—Switch interfaces, e.g. port details
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/10—Packet switching elements characterised by the switching fabric construction
    • H04L49/112—Switch control, e.g. arbitration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/10—Packet switching elements characterised by the switching fabric construction
    • H04L49/113—Arrangements for redundant switching, e.g. using parallel planes
    • H04L49/115—Transferring a complete packet or cell through each plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/15—Interconnection of switching modules
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/24—Resetting means
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/177—Initialisation or configuration control
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/30—Circuit design
    • G06F30/32—Circuit design at the digital level
    • G06F30/33—Design verification, e.g. functional simulation or model checking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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/24—Loading of the microprogram
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/50—Circuit switching systems, i.e. systems in which the path is physically permanent during the communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/10—Packet switching elements characterised by the switching fabric construction
    • H04L49/101—Packet switching elements characterised by the switching fabric construction using crossbar or matrix
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/15—Interconnection of switching modules
    • H04L49/1515—Non-blocking multistage, e.g. Clos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/25—Routing or path finding in a switch fabric

Definitions

  • the present invention relates generally to a computing system and more particularly to a system for hardware reconfiguration.
  • Electronic hardware with integrated circuits is used in virtually all electronic equipment today and has revolutionized the world of electronics.
  • the integrated circuits are used in digital computing systems, such as computers, televisions, cellular phones, mobile devices, and digital video cameras.
  • the present invention provides a method of operation of a computing system, including: providing a first cluster having a first kernel unit for managing a first reconfigurable hardware device; analyzing an application descriptor associated with an application; generating a first bitstream based on the application descriptor for loading the first reconfigurable hardware device, the first bitstream for implementing at least a first portion of the application; and implementing a first fragment with the first bitstream in the first cluster.
  • the present invention provides a computing system, including: a provision module for providing a first cluster having a first kernel unit for managing a first reconfigurable hardware device; a request module for analyzing an application descriptor associated with an application; an allocation module for generating a first bitstream based on the application descriptor for loading the first reconfigurable hardware device, the first bitstream for implementing at least a first portion of the application; and an execution module for implementing a first fragment with the first bitstream in the first cluster.
  • FIG. 1 is a computing system with hardware reconfiguration mechanism in an embodiment of the present invention.
  • FIG. 2 is an architecture diagram of the computing system.
  • FIG. 3 is a connection diagram of a cross-connection network of the reconfigurable hardware devices.
  • FIG. 4 is a connection diagram of a tandem kernel of the computing system.
  • FIG. 5 is a hardware block diagram of the computing system.
  • FIG. 6 is an architecture diagram of the application in the computing system.
  • FIG. 7 is a hardware block diagram of the microkernel.
  • FIG. 8 is an architecture diagram of one of the kernel modules.
  • FIG. 9 is an example of a hardware block diagram of the computing system.
  • FIG. 10 is a detailed diagram of the request module.
  • FIG. 11 is a detailed diagram of the allocation module.
  • FIG. 12 is a detailed diagram of the search module.
  • FIG. 13 is a flow chart of a method of operation of the computing system of FIG. 1 in a further embodiment of the present invention.
  • module includes hardware in the present invention in accordance with the context in which the term is used.
  • the hardware can include circuitry, programmable circuitry, computer, integrated circuit, integrated circuit cores, a pressure sensor, an inertial sensor, a microelectromechanical system (MEMS), passive devices, or a combination thereof.
  • MEMS microelectromechanical system
  • the computing system 100 can represent an adaptive architecture execution environment.
  • the computing system 100 can include a first electronic equipment 102 connected to a second electronic equipment 104 through a first communication path 106 .
  • the computing system 100 can include a third electronic equipment 108 connected to the second electronic equipment 104 through a second communication path 110 .
  • the first electronic equipment 102 , the second electronic equipment 104 , or the third electronic equipment 108 can represent a non-mobile device or a mobile device.
  • the first electronic equipment 102 , the second electronic equipment 104 , or the third electronic equipment 108 can be a server, a server farm, a computer, a grid-computing resource, a virtualized computer resource, a cloud computing resource, a router, a switch, a peer-to-peer distributed computing device, a network equipment, a storage enclosure, or a combination thereof.
  • the first electronic equipment 102 , the second electronic equipment 104 , or the third electronic equipment 108 can be a cellular phone, a personal digital assistant, a notebook computer, a multi-functional mobile communication device, or an entertainment device.
  • the first communication path 106 can represent a wireless network, a wired network, or a combination thereof for box-to-box connectivity.
  • the first communication path 106 can include wireless communication, wired communication, optical, ultrasonic, or a combination thereof.
  • Bluetooth, Infrared Data Association standard (IrDA), wireless fidelity (WiFi), and worldwide interoperability for microwave access (WiMAX) are examples of wireless communication for the first communication path 106 .
  • Ethernet, Fiber Channel, and Peripheral Component Interconnect (PCI) are also examples of wired communication for the first communication path 106 .
  • the second communication path 110 can represent a wireless network, a wired network, or a combination thereof for connectivity over a network.
  • the second communication path 110 can include wireless communication, wired communication, optical, ultrasonic, cloud network, or a combination thereof. Satellite communication, cellular communication, Bluetooth, Infrared Data Association standard (IrDA), wireless fidelity (WiFi), and worldwide interoperability for microwave access (WiMAX) are examples of wireless communication for the second communication path 110 .
  • Ethernet, digital subscriber line (DSL), fiber to the home (FTTH), and plain old telephone service (POTS) are also examples of wired communication for the second communication path 110 .
  • Each of the first electronic equipment 102 , the second electronic equipment 104 , and the third electronic equipment 108 can include a number of line cards 112 , which are defined as modular electronic sub-systems.
  • the line cards 112 can be connected together on a backplane or with cables for inside-a-box connectivity.
  • the line cards 112 can be connected together using connectivity methods including electrical connectors, optical fiber connectors, or wave-guide connectors.
  • Delay incurred by traversing the cross-connection network 302 can be regulated by managing a number of hierarchical levels in the cross-connection network 302 at implementation time.
  • the implementation time is a time when the reconfigurable hardware devices 202 , the line cards 112 of FIG. 1 , and a combination thereof are connected together through the cross-connection network 302 before the reconfigurable hardware devices 202 and the line cards 112 are available for operation.
  • Application logic that is not able to be fit or implemented into a single instance of the reconfigurable hardware devices 202 can require application synchronization at device input ports of each of the reconfigurable hardware devices 202 that are used to implement and execute the application logic.
  • Multiple approaches to the application synchronization can be supported assuming orthogonal application domains, which are groups of applications that are different and operate independently from each other.
  • the number of the application 304 can coexist in the computing system 100 and therefore can use the same system resources including a memory control interface (not shown) and a network control interface (not shown). Consistency of the application synchronization that applies the same terms and protocols can promote application independence and therefore scalability.
  • One of the reconfigurable hardware devices 202 can interface with another of the reconfigurable hardware devices 202 within one of the clusters 404 preferably through one of the kernel units 406 of the one of the clusters 404 .
  • one of the reconfigurable hardware devices 202 of one of the clusters 404 can interface directly with another of the reconfigurable hardware devices 202 of the one of the clusters 404 .
  • a number of the kernel units 406 and interconnections between the reconfigurable hardware devices 202 and the number of the kernel units 406 , among the number of the kernel units 406 , among the reconfigurable hardware devices 202 , or a combination thereof can represent portions of the cross-connection network 302 of FIG. 3 .
  • each of the clusters 404 having one of the kernel units 406 provides improved dynamic allocation of hardware resources because the application 304 of FIG. 3 can be fragmented, mapped, and executed with any number of the reconfigurable hardware devices 202 interface with each other through the one of the kernel units 406 .
  • the computing system 100 includes a dynamic reconfigurable computing platform without any external software intervention during real-time operation.
  • the computing system 100 can provide a complete hardware platform.
  • the tandem kernel 402 can include a communication interface 504 to provide communication between the tandem kernel 402 and another of the tandem kernel 402 .
  • the communication interface 504 can also provide communication between one of the kernel units 406 and another of the kernel units 406 .
  • the communication interface 504 can represent a network interface.
  • the communication interface 504 can be used for one of the kernel units 406 of the tandem kernel 402 to communicate with one of the kernel units 406 of another of the tandem kernel 402 through the communication network 502 .
  • the communication network 502 , the communication interface 504 , a number of the kernel units 406 , or a combination thereof can represent portions of the cross-connection network 302 of FIG. 3 .
  • a number of the tandem kernel 402 can be included on a number of the line cards 112 of FIG. 1 .
  • a number of the tandem kernel 402 can represent the first electronic equipment 102 of FIG. 1 , the second electronic equipment 104 of FIG. 1 , or the third electronic equipment 108 of FIG. 1 .
  • the computing system 100 can accommodate a number of different models of the reconfigurable hardware devices 202 , each of which can include different input/output (I/O) densities and different computing resources.
  • Suitability of the reconfigurable hardware devices 202 can depend on an application descriptor 506 , which is defined as information regarding a make-up or an attribute of the application 304 of FIG. 3 that determines how the reconfigurable hardware devices 202 are to be allocated for implementing the application 304 .
  • the application descriptor 506 can include resource requirements for implementing the application 304 of FIG. 3 .
  • the application descriptor 506 can include the operation feature including input/output-intensive (I/O-intensive) or compute-intensive, among other characteristics.
  • the application descriptor 506 can be used to determine a mix of the application 304 .
  • I/O-intensive refers to the application 304 that is preferably mapped to programmable hardware resources with a high I/O activity.
  • the high I/O activity refers to a number of input and output ports of a programmable hardware resource greater than a predefined numerical value of input and output ports.
  • the predefined numerical value of input and output ports can be 600.
  • I/O-intensive can represent I/O-heavy or high I/O density.
  • Compute-intensive refers to the application 304 that is preferably mapped to programmable hardware resources with a high compute resource capacity. Compute-intensive applies to the application 304 that demands a lot of computation compared to I/O-intensive that requires more input/output operations.
  • the application 304 that is I/O-intensive can be placed, routed, and executed more efficiently using a selected model of the reconfigurable hardware devices 202 that is designed for I/O-intensive applications than those for compute-intensive applications.
  • the application 304 that is compute-intensive can be placed, routed, and executed more efficiently using a different model of the reconfigurable hardware devices 202 that is designed for resource-intensive than those for I/O-intensive.
  • the computing system 100 can be tuned or configured by mixing the clusters 404 differently based on the application descriptor 506 .
  • the clusters 404 can represent kernel planes.
  • the application descriptor 506 of the application 304 can be particularly I/O-intensive but the application 304 has compute-intensive ancillary functionality that is most frequently unused.
  • the clusters 404 populated with high I/O density instances of the reconfigurable hardware devices 202 can be employed for execution of basic functionality of the application 304 .
  • the clusters 404 populated with compute resource intensive instances of the reconfigurable hardware devices 202 can be employed for execution of the compute-intensive ancillary functionality that is swapped in and out of the compute resource intensive instances of the reconfigurable hardware devices 202 .
  • Each of the clusters 404 can be analyzed to estimate an amount of time for implementing a functionality of the application 304 based on an actual capacity (or size) and an actual I/O density of the reconfigurable hardware devices 202 that are used to map the application 304 .
  • performance can be measured and a mix of the clusters 404 can be adjusted according to actual run-time characteristics.
  • the application mix refers to the number of the application 304 that need to be mapped to resources that are I/O-intensive, compute-intensive, or a combination thereof.
  • Placement of the clusters 404 can depend on the application mix. If an I/O-intensive functionality of the application 304 is localized in the reconfigurable hardware devices 202 , the clusters 404 that are I/O-intensive can be clustered together, thereby decongesting the communication network 502 of the computing system 100 . If an I/O-intensive functionality of the application 304 functions as a hub for a compute-intensive functionality, the clusters 404 that are I/O-intensive can be distributed amongst the clusters 404 that are compute-intensive.
  • Each of the kernel units 406 can include a microkernel 604 and kernel modules 606 .
  • the microkernel 604 can provide control, management, and communication capabilities for each of the kernel units 406 to interface with the reconfigurable hardware devices 202 of FIG. 2 to implement and execute functionality of the application 304 .
  • the kernel modules 606 augment functionality of the microkernel 604 by providing additional control and management capabilities that are not implemented in the microkernel 604 .
  • the kernel units 406 can be configured for the application 304 by compiling and synthesizing the kernel modules 606 expressly chosen for an application domain of the application 304 .
  • the application 304 can be loaded and executed on the reconfigurable hardware devices 202 .
  • the application domain refers to a type of a number of the application 304 that are grouped based on similar functionalities.
  • the application domain depends on problems that the number of the application 304 is implemented to solve.
  • the application domain can include encryption, computer vision, and synthetic-aperture radar that can be supported with high-performance computing functionalities implemented in the number of the application 304 .
  • the application 304 can be launched in a layer outside each of the kernel units 406 having the microkernel 604 and the kernel modules 606 .
  • the application 304 can be developed using a programming language including C++ and VHSIC hardware description language (VHDL) where VHSIC stands for very-high-speed integrated circuits.
  • VHSIC hardware description language
  • the application 304 can be developed with Open Computing Language (OpenCL) programs and compiled to run with an execution platform with only hardware using the reconfigurable hardware devices 202 .
  • OpenCL Open Computing Language
  • the application 304 can be mapped to and executed by the reconfigurable hardware devices 202 .
  • a method of mapping and implementing a representation or a bitstream of the application 304 can be managed by each of the kernel units 406 with the microkernel 604 and the kernel modules 606 .
  • FIG. 7 therein is shown a hardware block diagram of the microkernel 604 .
  • the microkernel 604 can be implemented with vital functions common to various types of a number of the application 304 of FIG. 3 that operates in a similar fashion across all application domains.
  • the microkernel 604 does not operate in a stand-alone form but instead with the kernel modules 606 .
  • the microkernel 604 can include operation functions including communications, logic multiplexing, security primitives, job scheduling, and distributed control.
  • the microkernel 604 is an interworking system of sub-functions, organized as shown in FIG. 7 .
  • the microkernel 604 can include the sub-functions that are stratified into three layers including a control layer 702 , a support layer 704 , and a run-time layer 706 .
  • the control layer 702 performs a job control and includes a microkernel interface (not shown).
  • the control layer 702 can include a user interface unit 708 and an application manager 710 for performing control functions including session management, control plane security, and job scheduling.
  • the support layer 704 provides scheduling support and network management.
  • the support layer 704 can include a module manager 712 , a resource manager 714 , and an event manager 716 for performing support functions including scenario validation, event handling, and remote kernel interface management.
  • the run-time layer 706 provides an application run-time plant.
  • the run-time layer 706 can include run-time blocks including an intra-cluster communication unit 718 having a buffer manager 720 and a virtual bus 722 with a switch fabric 724 .
  • the run-time layer 706 can include the run-time blocks including a number of memory devices 726 and an inter-cluster communication unit 728 .
  • the run-time layer 706 can include the run-time blocks for performing run-time functions including interfacing with the reconfigurable hardware devices 202 and performing application fragment interconnect, signal management, network interface, and network and application interface security.
  • the microkernel 604 can include a schedule engine 730 for scheduling portions of a number of the reconfigurable hardware devices 202 .
  • the schedule engine 730 can include the application manager 710 , the module manager 712 , the resource manager 714 , and the event manager 716 to support the scheduling.
  • Sub-blocks of the control layer 702 , the support layer 704 , and the run-time layer 706 can be connected to each other, the reconfigurable hardware devices 202 , and the kernel modules 606 .
  • the control layer 702 can interface with the kernel modules 606 and the support layer 704 .
  • the support layer 704 can interface with the control layer 702 and the run-time layer 706 .
  • the run-time layer 706 can interface with the support layer 704 , the reconfigurable hardware devices 202 , and the kernel modules 606 .
  • the microkernel 604 can provide primitives that implement functionality including application module scheduling and maintenance, seamless application fragment interaction, and high-performance application communication.
  • the term “primitives” refers to a simple operation for executing a relatively more complex operation than the simple operation.
  • the primitives can represent low-level commands that are used to execute relatively high-level commands.
  • the application module scheduling and maintenance can include thread maintenance and module swapping.
  • the seamless application fragment interaction can include interconnection and synchronization.
  • the thread maintenance monitors instantaneous application needs and regulates allocation of resources to the application 304 .
  • the thread maintenance is performed for multiple applications or processes.
  • the thread maintenance can monitor the instantaneous application needs of the application 304 and allocate ancillary logic of the reconfigurable hardware devices 202 that has been swapped out to be used by the application 304 .
  • ancillary refers to spare logic gates that are swapped in to implement a function and swapped out to be available to implement another function when the spare logic gates are subsequently needed.
  • the thread maintenance can determine that a pipeline stall associated with feedback can require treatment.
  • the module swapping circumscribes or includes functionality associated with process scheduling including networked database support, identification of appropriate application fragment, run-time application fragment place and route, attachment and registration of application fragment alarms, and intra-application fragment signal handling configuration.
  • the microkernel 604 can facilitate run-time synchronization at application grain boundaries including flow-control and management of pipeline stalls involving pipelines that span the application grain boundaries.
  • fragment refers to a portion of the application 304 .
  • the microkernel 604 can also provide for bus interconnection and reliable delivery of application signal information from outputs to fanned-out inputs at application fragment grain boundaries.
  • the application fragment grain boundaries are perimeters of groups of programmable blocks in the reconfigurable hardware devices 202 , where interconnects or wires are connected between the groups.
  • the microkernel 604 can provide a low-overhead communication infrastructure to the application 304 developed as any combination of software and hardware on top of or outside the microkernel 604 and the kernel modules 606 . Wrappers or interfaces for the application 304 can be written in hardware or software outside the microkernel 604 and the kernel modules 606 to seamlessly adapt the low-overhead communication infrastructure to a number of protocols.
  • Each of the kernel units 406 of FIG. 4 can include the kernel modules 606 in addition to the microkernel 604 of FIG. 6 to provide hardware platform functionality that can spread across a number of the line cards 112 of FIG. 1 , the tandem kernel 402 of FIG. 4 , the kernel units 406 , or a combination thereof.
  • the kernel units 406 can be shaped or configured for the application domain with the kernel modules 606 .
  • Each of the kernel modules 606 can include a microkernel interface unit 802 .
  • the microkernel interface unit 802 provides communication capability for each of the kernel modules 606 to communicate with the microkernel 604 through a kernel expansion bus 804 .
  • the kernel expansion bus 804 provides connectivity between the microkernel interface unit 802 and the microkernel 604 .
  • the microkernel interface unit 802 can support a variety of bus widths and protocols appropriate to functionality of the microkernel 604 .
  • Each of the kernel modules 606 can include a security unit 806 to monitor a kernel module security status and determine whether each of the kernel units 406 operates in a secured mode.
  • Each of the kernel modules 606 can include a configurable functionality unit 808 that interfaces between the microkernel interface unit 802 and user logic devices.
  • the user logic devices are non-kernel logic devices that are implemented outside the kernel units 406 .
  • the user logic devices can be used to transmit application related information of the application 304 of FIG. 3 to the kernel units 406 for authentication, configuration, and management of the reconfigurable hardware devices 202 of FIG. 2 .
  • the configurable functionality unit 808 can interface with the user logic devices through a communication bus including Peripheral Component Interconnect (PCI) or a system bus on a motherboard or a system board.
  • PCI Peripheral Component Interconnect
  • the configurable functionality unit 808 includes developed supplemental logic to support a number of configuration functionalities.
  • the configuration functionalities can be associated with the policy including module swapping rules, privilege and authentication rules, scheduling rules, function cache allocation, database management, and managing events and event relationships.
  • the configuration functionalities can be associated with interface domain diversity, high-usage application domain functions, issues of waiting logic, and system scalability.
  • interface domain diversity can imply behavioral sub classification.
  • the kernel modules 606 house or include interface functionality based on a sub-classification because different interface domains have different characteristics.
  • the different characteristics or differentiation can be based on speed and latency. Latency can be affected by inherent equipment constraints or by physical distance between nodes that represent locations of the reconfigurable hardware devices 202 .
  • the kernel modules 606 can be implemented with the functionalities based on application parameters or features that are not implemented in the microkernel 604 .
  • the kernel modules 606 can be implemented with functionalities including supports for shell programs and file systems.
  • the microkernel 604 and the kernel modules 606 can be implemented with any number of electronic components including an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA).
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the microkernel 604 and the kernel modules 606 can altogether be implemented with an ASIC, an FPGA, or a combination thereof.
  • the computing system 100 can include a hardware platform in a form of a kernel that supports swappable, re-locatable hardware applications.
  • the hardware platform includes an interworking set of the control layer 702 of FIG. 7 , the support layer 704 of FIG. 7 , and the run-time layer 706 of FIG. 7 .
  • the term “run-time” refers to a time when the application 304 of FIG. 3 is executed in the computing system 100 .
  • the computing system 100 can include a provision module 902 for providing and configuring the clusters 404 of FIG. 4 .
  • the provision module 902 can generate a first cluster 904 , which is one of the clusters 404 .
  • the first cluster 904 can be generated by grouping a first kernel unit 906 having a first microkernel 908 with a first user interface unit 910 .
  • the first cluster 904 can include a number of first reconfigurable hardware devices 912 .
  • the first reconfigurable hardware devices 912 can be grouped together into the first cluster 904 based on the application descriptor 506 of FIG. 5 . For example, instances of the first reconfigurable hardware devices 912 that are compute-intensive, I/O-intensive, or a combination thereof can be grouped together. The instances of the first reconfigurable hardware devices 912 can be grouped together with the switching and buffering mechanism for transmission of information or data among the instances. The instances can communicate with each other through the first kernel unit 906 or optionally directly to each other.
  • the first kernel unit 906 is one of the kernel units 406 of FIG. 4 .
  • the first microkernel 908 is the microkernel 604 of FIG. 6 .
  • the first user interface unit 910 is the user interface unit 708 of FIG. 7 of the microkernel 604 .
  • the first reconfigurable hardware devices 912 are the reconfigurable hardware devices 202 of FIG. 2 connected to the one of the kernel units 406 .
  • the first kernel unit 906 can be implemented and dynamically reconfigured to manage the first reconfigurable hardware devices 912 .
  • the hardware block diagram depicts two of the first reconfigurable hardware devices 912 , although it is understood that any number of the first reconfigurable hardware devices 912 can be connected to the first kernel unit 906 .
  • the provision module 902 can generate a second cluster 914 , which is another of the clusters 404 .
  • the second cluster 914 can be generated by grouping a second kernel unit 916 having a second microkernel 918 with a second user interface unit 920 .
  • the second cluster 914 can include a number of second reconfigurable hardware devices 922 .
  • the second reconfigurable hardware devices 922 can be grouped together into the second cluster 914 based on the application descriptor 506 . For example, instances of the second reconfigurable hardware devices 922 that are compute-intensive, I/O-intensive, or a combination thereof can be grouped together. The instances of the second reconfigurable hardware devices 922 can be grouped together with the switching and buffering mechanism for transmission of information or data among the instances. The instances can communicate with each other through the second kernel unit 916 or optionally directly to each other.
  • the second kernel unit 916 is another of the kernel units 406 .
  • the second microkernel 918 is another of the microkernel 604 .
  • the second user interface unit 920 is another of the user interface unit 708 of the another of the microkernel 604 .
  • the second reconfigurable hardware devices 922 are the reconfigurable hardware devices 202 connected to the another of the kernel units 406 .
  • the first cluster 904 and the second cluster 914 can be included in one of the line cards 112 of FIG. 1 .
  • the first cluster 904 can be included in one of the line cards 112 and the second cluster 914 can be included in another of the line cards 112 .
  • the first cluster 904 and the second cluster 914 can be included in the tandem kernel 402 of FIG. 4 .
  • the first cluster 904 and the second cluster 914 can be included in the tandem kernel 402 and another of the tandem kernel 402 , respectively.
  • the first cluster 904 and the second cluster 914 can represent multiple instances of the clusters 404 .
  • the multiple instances of the clusters 404 can represent kernel planes fused into a single system image from an application perspective providing arbitrary scale of applications.
  • the single system image can represent a merged image of the computing system 100 .
  • the first cluster 904 and the second cluster 914 can be coupled to each other.
  • the first cluster 904 and the second cluster 914 can be directly connected in a back-to-back or point-to-point connection.
  • the first cluster 904 and the second cluster 914 can optionally be connected through the communication network 502 of FIG. 5 , the communication interface 504 of FIG. 5 , or a combination thereof.
  • the first cluster 904 and the second cluster 914 can be initially configured with the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 , respectively.
  • the first cluster 904 and the second cluster 914 can be configured or provided based on the application descriptor 506 since the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 , respectively, can be selected based on the application descriptor 506 to support the application 304 .
  • the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 can be specified by a hardware platform developer of the application 304 or a system administrator of the computing system 100 .
  • the computing system 100 can include a request module 924 for evaluating a user request 926 to initialize the application 304 .
  • the request module 924 provides a communication capability for interfacing with the user of the computing system 100 , such as the hardware platform developer or the system administrator.
  • the request module 924 can be coupled to the provision module 902 .
  • the computing system 100 can include an allocation module 928 for performing scheduling and optimization to generate placement and interconnection of reconfigurable resources 930 for implementing the application 304 .
  • the allocation module 928 can be coupled to the request module 924 .
  • the reconfigurable resources 930 are defined as programmable logic blocks and interconnects in the first reconfigurable hardware devices 912 , the second reconfigurable hardware devices 922 , or a combination thereof.
  • the reconfigurable resources 930 include a number of programmable devices, embedded memories, locations of the programmable devices and the embedded memories, and interconnections among the programmable devices.
  • the programmable devices can include logic gates, flip-flops, and memory elements.
  • the allocation module 928 can perform a scheduling procedure 932 and an optimization procedure 934 for implementing functions of the application 304 .
  • the scheduling procedure 932 is a method that determines which and when microkernel resources 936 are allocated to perform the optimization procedure.
  • the optimization procedure is a method that determines the reconfigurable resources 930 in the first reconfigurable hardware devices 912 , the second reconfigurable hardware devices 922 , or a combination thereof that are used to implement the functionalities of the application 304 .
  • the microkernel resources 936 are defined as resources in the microkernel 604 including logic gates, storage elements, interconnections, and buffer allocation for implementation of the application 304 .
  • the microkernel resources 936 can include portions of the first user interface unit 910 , the application manager 710 of FIG. 7 , the module manager 712 of FIG. 7 , the resource manager 714 of FIG. 7 , the event manager 716 of FIG. 7 , the intra-cluster communication unit 718 of FIG. 7 , the buffer manager 720 of FIG. 7 , the virtual bus 722 of FIG. 7 , the switch fabric 724 of FIG. 7 , the memory devices 726 of FIG. 7 , and the inter-cluster communication unit 728 of FIG. 7 .
  • the allocation module 928 can generate a first bitstream 940 , an additional bitstream 942 , a second bitstream 944 , or a combination thereof.
  • the first bitstream 940 , the additional bitstream 942 , and the second bitstream 944 are defined as sequences of digital information represented in binary digits.
  • the first bitstream 940 and the additional bitstream 942 can be used for implementing different portions, such as a first portion and a second portion, of the application 304 when the application 304 cannot be implemented with just the first bitstream 940 .
  • the application 304 can be partitioned into a number of application fragments 946 , which are defined as portions of the application 304 .
  • the application fragments 946 can include a first fragment 948 , an additional fragment 950 , and a second fragment 952 .
  • the first fragment 948 , the additional fragment 950 , and the second fragment 952 are defined as portions of the application 304 .
  • the first fragment 948 , the additional fragment 950 , and the second fragment 952 can be implemented using the first bitstream 940 , the additional bitstream 942 , and the second bitstream 944 , respectively.
  • the first fragment 948 and the additional fragment 950 can be implemented using the first cluster 904 .
  • the second fragment 952 can be implemented using the second cluster 914 .
  • the first bitstream 940 , the additional bitstream 942 , and the second bitstream 944 can represent hardware encodings of portions of the application 304 .
  • the first bitstream 940 and the additional bitstream 942 can be loaded into any number of the first reconfigurable hardware devices 912 .
  • the second bitstream 944 can be loaded into one of the second reconfigurable hardware devices 922 .
  • the allocation module 928 can generate just the first bitstream 940 . Also for example, if the application 304 cannot be implemented using the contiguous section, the allocation module 928 can generate the additional bitstream 942 in addition to the first bitstream 940 .
  • first bitstream 940 and the additional bitstream 942 can be implemented by the first bitstream 940 and the additional bitstream 942 .
  • the first bitstream 940 and the additional bitstream 942 can be loaded into any number of the first reconfigurable hardware devices 912 , wherever there are programmable blocks and interconnects in the first reconfigurable hardware devices 912 that are available for implementing the application 304 .
  • the first bitstream 940 and the additional bitstream 942 can be loaded into only one of the first reconfigurable hardware devices 912 .
  • the first bitstream 940 can be loaded into one of the first reconfigurable hardware devices 912 and the additional bitstream 942 can be loaded into an additional reconfigurable hardware device 954 , which is another of the first reconfigurable hardware devices 912 in the first cluster 904 .
  • the functionalities of the application 304 can be implemented using the first cluster 904 , only the first bitstream 940 can be generated.
  • the functionalities of the application 304 cannot be implemented using just the first cluster 904 , the functionalities of the application 304 can be implemented using the first cluster 904 and the second cluster 914 , and thus the first bitstream 940 and the second bitstream 944 can be generated.
  • the application 304 can be partitioned into a number of the application fragments 946 .
  • the first bitstream 940 and the second bitstream 944 can be generated for the first fragment 948 and the second fragment 952 , respectively.
  • the allocation module 928 is described to include only the first bitstream 940 and the second bitstream 944 , although it is understood that the allocation module 928 can include any number of the first bitstream 940 , the second bitstream 944 , or a combination thereof for implementing all instances of the application fragments 946 .
  • the first bitstream 940 and the second bitstream 944 can include encoding of the first fragment 948 and the second fragment 952 , respectively.
  • the first bitstream 940 , the second bitstream 944 , or a combination thereof can be generated based on the application descriptor 506 .
  • the application descriptor 506 when the application descriptor 506 is I/O-intensive, instances of the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 , which are capable of performing the high I/O activity, can be loaded with the first bitstream 940 and the second bitstream 944 , respectively.
  • instances of the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 which include the high compute resource capacity, can be loaded with the first bitstream 940 and the second bitstream 944 , respectively.
  • the computing system 100 can include an execution module 956 for implementing the application 304 .
  • the first bitstream 940 , the additional bitstream 942 , the second bitstream 944 , or a combination thereof can be used to implement and execute the application 304 .
  • the first bitstream 940 and the additional bitstream 942 can be loaded into any number of the first reconfigurable hardware devices 912 for execution of the first fragment 948 and the additional fragment 950 , respectively.
  • the second bitstream 944 can be loaded into one of the second reconfigurable hardware devices 922 for execution of the second fragment 952 .
  • the execution module 956 can be coupled to the allocation module 928 . There can be a number of independently operating instances of the application 304 concurrently executed in the first reconfigurable hardware devices 912 , the second reconfigurable hardware devices 922 , or a combination thereof.
  • the provision module 902 for generating the first cluster 904 having the first kernel unit 906 provides improved scalability because the first kernel unit 906 is capable of managing any number of the first reconfigurable hardware devices 912 .
  • provision module 902 for generating the second cluster 914 having the second kernel unit 916 provides improved scalability because the second kernel unit 916 is capable of managing any number of the second reconfigurable hardware devices 922 .
  • the request module 924 for analyzing the application descriptor 506 provides improved area and performance since the request module 924 is capable of determining which instances of the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 that are I/O-intensive or compute-intensive in order to efficiently implement the application 304 .
  • the allocation module 928 provides improved area and performance because the allocation module 928 is able to effectively generate the first bitstream 940 and the second bitstream 944 since the instances of the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 that are I/O-intensive or compute-intensive are known based on the application descriptor 506 .
  • the execution module 956 provides improved performance since the application 304 is able to be executed using multiple instances of the kernel units 406 .
  • the first fragment 948 and the second fragment 952 of the application 304 are simultaneously executed using the first kernel unit 906 and the second kernel unit 916 , respectively.
  • the allocation module 928 provides improved performance by generating the additional bitstream 942 to reduce execution time of the application 304 by simultaneously implementing the first bitstream 940 and the additional bitstream 942 using multiple instances of the first reconfigurable hardware devices 912 .
  • the request module 924 can include a load module 1002 to provide a communication capability for interfacing with the user of the computing system 100 of FIG. 1 .
  • the load module 1002 can be implemented with a portion of the first user interface unit 910 of FIG. 9 , which provides authentication and session support.
  • the load module 1002 can be implemented with the first user interface unit 910 to provide an interface for the user to submit a session command 1004 .
  • the session command 1004 can be used to establish a login session 1006 to request the application 304 of FIG. 3 to be loaded.
  • the login session 1006 is defined as a duration in which communication is permitted.
  • the login session 1006 can include a unique session identifier that distinguishes the login session 1006 from other sessions.
  • the login session 1006 can be authenticated with a password to prevent an unauthorized access.
  • the first user interface unit 910 can provide an interface for the user to directly log on.
  • the first user interface unit 910 can provide an interface for the first microkernel 908 of FIG. 9 to send the session command 1004 to the second user interface unit 920 of FIG. 9 to establish or create the login session 1006 in the second cluster 914 of FIG. 9 .
  • the session command 1004 is defined as an instruction that starts or ends a user session.
  • the session command 1004 can include a login command and a logout command.
  • the login command establishes the login session 1006 for a user name.
  • a session manager of the second user interface unit 920 can recognize the login command without a need for an authenticated session.
  • the login session 1006 can be created in the second cluster 914 so that the first user interface unit 910 can continue to communicate with the second user interface unit 920 .
  • the login command requires a persisted registration of the user name and a submission of the password from the user.
  • a successful login with a correct user name and the password can result in a return of a session identifier for a newly created user session.
  • the return of the session identifier can be performed by the second user interface unit 920 .
  • the logout command dissolves the login session 1006 tagged with the unique session identifier.
  • the logout command can return all occupied resources in the microkernel resources 936 of FIG. 9 , the reconfigurable resources 930 of FIG. 9 , or a combination thereof to respective free lists of available resources for re-use.
  • the load module 1002 can generate a load command 1008 for the application 304 per the user's request for the application 304 to be loaded.
  • the load command 1008 is defined as an instruction for loading the application 304 to subsequently perform the scheduling procedure 932 of FIG. 9 and the optimization procedure 934 of FIG. 9 .
  • the application 304 can be received by the first cluster 904 of FIG. 9 using the first user interface unit 910 for interfacing with the user.
  • the first user interface unit 910 and the second user interface unit 920 can also provide the interface for the first microkernel 908 and the second microkernel 918 of FIG. 9 , respectively, to communicate with each other through the communication network 502 of FIG. 5 , the communication interface 504 of FIG. 5 , or a combination thereof.
  • the first microkernel 908 can send a login request using the session command 1004 to the second microkernel 918 to establish the login session 1006 .
  • a portion of the functionalities of the application 304 can be implemented using the second cluster 914 and thus the second bitstream 944 of FIG. 9 can be generated by the second microkernel 918 .
  • the user can provide the application descriptor 506 of FIG. 5 of the application 304 to indicate if the application 304 is I/O-intensive or compute-intensive.
  • the load module 1002 can be implemented with a portion of the first user interface unit 910 for interfacing with the user.
  • the request module 924 can include an analyze module 1010 to analyze the application descriptor 506 associated with the application 304 that is to be implemented in the first cluster 904 , the second cluster 914 , or a combination thereof.
  • the analyze module 1010 can analyze the application descriptor 506 for the load command 1008 .
  • the application descriptor 506 can be analyzed so that the application 304 can be implemented with a number of specific instances of the first reconfigurable hardware devices 912 of FIG. 9 , the second reconfigurable hardware devices 922 of FIG. 9 , or a combination thereof.
  • the analyze module 1010 can be coupled to the load module 1002 .
  • the analyze module 1010 can record execution times and numbers of input/output (I/O) ports of the reconfigurable resources 930 that have been used to implement previous instances of the application 304 using the first cluster 904 , the second cluster 914 , or a combination thereof.
  • the execution times can be recorded along with previous instances of the application descriptor 506 of previous instances of the application 304 .
  • the analyze module 1010 can analyze the application descriptor 506 by determining which of the first cluster 904 , the second cluster 914 , or a combination thereof that can be used to implement a current instance of the application 304 based on the execution times and the numbers of input/output ports.
  • the analyze module 1010 can indicate which of the first cluster 904 , the second cluster 914 , or a combination thereof has the shortest execution time and thus would be the best resource for implementing the current instance of the application 304 . Also for example, if the application descriptor 506 indicates that the current instance of the application 304 is I/O-intensive, the analyze module 1010 can indicate which of the first cluster 904 , the second cluster 914 , or a combination thereof has the most number of I/O ports for implementing the current instance of the application 304 .
  • the application descriptor 506 can be analyzed at any specific instance of time.
  • the application descriptor 506 can be analyzed periodically at a specific time of day when the system is least busy on an average during each day or within a specific duration after receiving the load command 1008 .
  • the request module 924 can include a launch module 1012 to initiate a procedure to launch and execute the application 304 after the launch module 1012 receives the load command 1008 .
  • the launch module 1012 can be coupled to the analyze module 1010 .
  • the launch module 1012 can be implemented with a portion of an application agent 1014 in the resource manager 714 of FIG. 7 to receive and evaluate the load command 1008 .
  • the application agent 1014 can interface with the first user interface unit 910 .
  • the application agent 1014 monitors and controls activity among the control layer 702 of FIG. 7 , the support layer 704 of FIG. 7 , and the run-time layer 706 of FIG. 7 for the implementation of the application 304 after the login session 1006 has been authorized by the first user interface unit 910 .
  • the launch module 1012 can be implemented with a portion of an application state logic 1016 in the application manager 710 of FIG. 7 .
  • the application state logic 1016 tracks states of the microkernel resources 936 and ensures transitions of the states to support loading of the application 304 upon receiving the load command 1008 .
  • the resource manager 714 provides a capability to launch the application 304 and allocate the microkernel resources 936 in the microkernel 604 of FIG. 6 to implement the application 304 using the scheduling procedure 932 and the optimization procedure 934 .
  • the resource manager 714 can include a communication manager for controlling the switch fabric 724 of FIG. 7 by setting up and tearing down port-to-multiport connections across a close switch in the switch fabric 724 .
  • the communication manager also configures the virtual bus 722 of FIG. 7 , which is a collection of signal wires that are managed or synchronized altogether by the same control signals for transmission of data or information between the first reconfigurable hardware devices 912 .
  • the resource manager 714 can include a dispatcher to set up a configuration of the first reconfigurable hardware devices 912 and, upon inception of a request for loading the application 304 , data structures in the memory devices 726 of FIG. 7 required to support the application 304 .
  • the event manager 716 of FIG. 7 evaluates events and provides fault or error notifications to subsystems in the control layer 702 , the support layer 704 , and the run-time layer 706 .
  • the event manager 716 can inform the application manager 710 , the module manager 712 of FIG. 7 , the resource manager 714 , or a combination thereof that an alteration in priorities associated with the microkernel resources 936 and the reconfigurable resources 930 for the implementation of the application fragments 946 of FIG. 9 .
  • the alteration in the priorities can include addition, subtraction, activation, suspension, or consolidation of the microkernel resources 936 , the reconfigurable resources 930 , or a combination thereof.
  • the intra-cluster communication unit 718 of FIG. 7 provides switching and buffering mechanism for transmission of information or data among the first reconfigurable hardware devices 912 or among the second reconfigurable hardware devices 922 .
  • the memory devices 726 provide signal buffers for data to flow between the application fragments 946 implemented in the first reconfigurable hardware devices 912 .
  • the inter-cluster communication unit 728 of FIG. 7 provides switching and buffering mechanism for transmission of information or data between the first kernel unit 906 of FIG. 9 and the second kernel unit 916 of FIG. 9 .
  • the inter-cluster communication unit 728 can include the communication interface 504 .
  • the inter-cluster communication unit 728 can interface with the communication network 502 .
  • the inter-cluster communication unit 728 can provide communication between the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 through the first kernel unit 906 and the second kernel unit 916 .
  • the application agent 1014 can inform the application state logic 1016 that the application 304 is to be launched after the application agent 1014 receives the load command 1008 .
  • the application state logic 1016 in the application manager 710 can accept directives from the application agent 1014 .
  • the directives are commands that are used to control the microkernel resources for launching and implementing the application 304 .
  • the load module 1002 provides improved scalability by providing the session command 1004 to establish the login session 1006 at the second cluster 914 for implementing the functionalities of the application 304 using not only the first cluster 904 but also the second cluster 914 .
  • the allocation module 928 can include a specification module 1102 for performing the scheduling procedure 932 of FIG. 9 .
  • the specification module 1102 can be informed by the launch module 1012 of FIG. 10 that the application 304 of FIG. 3 is to be launched.
  • the specification module 1102 can be implemented with a portion of a schedule formation unit 1104 in the application manager 710 of FIG. 7 .
  • the application state logic 1016 of FIG. 10 can inform the schedule formation unit 1104 that the application 304 is to be launched.
  • the schedule formation unit 1104 performs the scheduling procedure 932 to determine when the optimization procedure is scheduled to be performed for implementation of the application 304 .
  • the term “implementation” refers to scheduling, optimization, and execution of the application fragments 946 of FIG. 9 .
  • the optimization procedure 934 of FIG. 9 is scheduled by the schedule formation unit 1104 assigning a number of time slots 1106 reserved for the optimization procedure 934 .
  • Each of the time slots 1106 is defined as a non-zero amount of time that is not used and thus available for the optimization procedure 934 .
  • Each of the time slots 1106 can represent a scheduling granularity or a unit of time.
  • the schedule formation unit 1104 can generate a factor profile 1108 , which is defined as information that is used for the optimization procedure 934 to perform.
  • the factor profile 1108 can represent an optimization specification that is used to control the optimization procedure 934 .
  • the factor profile 1108 can be generated with scheduling information 1110 , which is defined as parameter associated with the application 304 for control of the optimization procedure 934 .
  • the scheduling information 1110 can include the time slots 1106 and the microkernel resources 936 of FIG. 9 that are used by the optimization procedure 934 .
  • the scheduling information 1110 can include a time limit for how long the optimization procedure 934 is to be performed. When the optimization procedure 934 is performed longer than the time limit, the optimization procedure 934 can automatically restart its procedure up to a maximum iteration number.
  • the scheduling information 1110 can specify an optimization algorithm type that is used by the optimization procedure 934 to select an algorithm for performing an optimization.
  • the scheduling information 1110 can include a maximum fragment number that is used by the optimization procedure 934 to determine up to how many of the application fragments 946 that the optimization procedure 934 can generate.
  • the maximum fragment number can be applied when the application 304 cannot be implemented due to lack of the microkernel resources 936 , the reconfigurable resources 930 of FIG. 9 , or a combination thereof.
  • the scheduling information 1110 can include the application descriptor 506 of FIG. 5 so that the optimization procedure 934 can determine instances of the reconfigurable resources 930 that are capable of handling I/O-intensive or compute-intensive functionalities.
  • the allocation module 928 can include an optimization module 1112 for performing the optimization procedure 934 .
  • the optimization module 1112 can be implemented with a portion of a scenario formulation unit 1114 in the module manager 712 of FIG. 7 .
  • the scenario formulation unit 1114 performs the optimization procedure 934 .
  • the optimization module can be coupled to the specification module 1102 .
  • the scenario formulation unit 1114 can receive the factor profile 1108 from the schedule formation unit 1104 to perform the optimization procedure 934 to determine the reconfigurable resources 930 that are to be used to implement the functionalities of the application 304 .
  • the scenario formulation unit 1114 can perform the optimization procedure 934 at the time slots 1106 specified by the factor profile 1108 .
  • the scenario formulation unit 1114 can perform the optimization procedure 934 to determine the reconfigurable resources 930 based on the scheduling information 1110 .
  • the scenario formulation unit 1114 can retrieve information from a first database 1116 provided by the module manager 712 of the first microkernel 908 of FIG. 9 .
  • the first database 1116 is defined as a collection of information for determining the microkernel resources 936 and the reconfigurable resources 930 for the implementation of the application 304 .
  • the first database 1116 can include information that can indicate or be used to determine which instances of the microkernel resources 936 that are not used and thus available for the scheduling procedure 932 to scheduling the time slots 1106 for the optimization procedure 934 . Also for example, the first database 1116 can include information that can indicate or be used to determine which instances of the reconfigurable resources 930 that are not used and thus available for the optimization procedure 934 .
  • the first database 1116 can include application information 1118 including an application identification (ID), a sector count, an input count, and an output count.
  • the application identification provides a unique identifier of the application 304 when the login session 1006 of FIG. 10 is established.
  • the sector count indicates a number of partitions or portions in specific instances of the reconfigurable resources 930 allocated for implementation of the application 304 .
  • the input count and the output count indicate a number of input ports and output ports, respectively, of the partitions or the portions in the specific instances of the reconfigurable resources 930 .
  • the first database 1116 also includes connection information 1120 associated with routing of signals among the first reconfigurable hardware devices 912 of FIG. 9 or among the second reconfigurable hardware devices 922 of FIG. 9 .
  • the connection information 1120 can be associated with routing of signals between the first kernel unit 906 of FIG. 9 and the second kernel unit 916 of FIG. 9 .
  • the connection information 1120 can be associated with routing of signals between the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 through the first kernel unit 906 and the second kernel unit 916 , respectively.
  • connection information 1120 can include switch interconnections and input/output switch ports associated with the buffer manager 720 of FIG. 7 and the switch fabric 724 of FIG. 7 in the virtual bus 722 of FIG. 7 .
  • the connection information 1120 can include switch interconnections and input/output switch ports associated with the communication interface 504 of FIG. 5 for routing of signals between the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 through the communication network 502 of FIG. 5 .
  • the connection information 1120 can be associated with routing of signals between the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 through the first kernel unit 906 and the second kernel unit 916 .
  • the scenario formulation unit 1114 can retrieve not only the first database 1116 but also a second database 1122 .
  • the second database 1122 provides similar functionalities as the first database 1116 except that the second database 1122 is included in another of the module manager 712 of the second microkernel 918 of FIG. 9 .
  • the first database 1116 and the second database 1122 can represent a network database that provides an integration of information for determining the microkernel resources 936 and the reconfigurable resources 930 in both the first microkernel 908 and the second microkernel 918 for the implementation of the application fragments 946 .
  • the optimization module 1112 can detect a slack capacity 1124 in the second cluster 914 .
  • the slack capacity 1124 is defined as a number of resources available for purposes of implementing a number of the application fragments 946 .
  • the slack capacity 1124 can include the microkernel resources 936 , the reconfigurable resources 930 , or a combination thereof in the second cluster 914 .
  • the slack capacity 1124 can be detected by the optimization module 1112 communicating with the second user interface unit 920 of FIG. 9 with the session command 1004 of FIG. 10 .
  • the optimization module 1112 can access the second database 1122 .
  • the optimization module 1112 can detect the slack capacity 1124 in the second cluster 914 by determining if there are instances of the microkernel resources 936 and instances of the reconfigurable resources 930 that are not used and thus available.
  • the slack capacity 1124 can be detected for the scheduling procedure 932 and the optimization procedure 934 to be performed in the second cluster 914 .
  • the optimization module 1112 can generate the second fragment 952 based on the slack capacity 1124 .
  • the second fragment 952 can be generated since the optimization module 1112 detects that there is the slack capacity 1124 available for the scheduling procedure 932 and the optimization procedure 934 to be performed in the second cluster 914 .
  • the optimization module 1112 can request the second microkernel 918 to perform the scheduling procedure 932 and the optimization procedure 934 in the second cluster 914 to generate the second bitstream 944 of FIG. 9 for the second fragment 952 .
  • the optimization module 1112 can be implemented with a scenario optimizer 1126 in the resource manager 714 of FIG. 7 .
  • the scenario optimizer 1126 provides an array of processing engines for performing the optimization procedure 934 for the first fragment 948 and the second fragment 952 using the reconfigurable resources 930 in the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 , respectively.
  • the scenario optimizer 1126 performs the optimization procedure 934 with information from the first database 1116 and the second database 1122 retrieved by the scenario formulation unit 1114 and sent to the scenario optimizer 1126 .
  • the optimization module 1112 can include a search module 1128 for determining the reconfigurable resources 930 and the microkernel resources 936 across the first cluster 904 and the second cluster 914 .
  • the search module 1128 can determine the reconfigurable resources 930 and the microkernel resources 936 based on an optimization result 1130 of the optimization procedure 934 performed by the scenario optimizer 1126 .
  • the optimization result 1130 provides an indication whether the optimization procedure 934 succeeds or fails.
  • the search module 1128 can be implemented with the first user interface unit 910 of FIG. 9 of the first microkernel 908 to communicate with the second user interface unit 920 of the second microkernel 918 to establish the login session 1006 at the second kernel unit 916 .
  • the search module 1128 can access the second database 1122 to determine if the second microkernel 918 has the microkernel resources 936 and the second reconfigurable hardware devices 922 have the reconfigurable resources 930 for implementing the second fragment 952 .
  • the search module 1128 can continue its search throughout the communication network 502 .
  • the search module 1128 can continue its search until the search module 1128 detects any other instances of the clusters 404 of FIG. 4 that can sufficiently provide the microkernel resources 936 and the reconfigurable resources 930 for implementing the second fragment 952 .
  • the optimization result 1130 can include reservation tables 1132 , which are collection of information associated with the microkernel resources 936 and the reconfigurable resources 930 that are used to implement the application fragments 946 .
  • the reservation tables 1132 can represent a prescription for placement and interconnection of the application fragments 946 into a complete image of the application 304 .
  • the reservation tables 1132 can be provided by the first database 1116 , the second database 1122 , or a combination thereof.
  • the optimization parameters are a set of constraints that are provided by the factor profile 1108 .
  • the optimization parameters can represent the scheduling information 1110 including the time slots 1106 , the microkernel resources 936 , the time limit, the optimization algorithm type, the maximum fragment number, and user input/output pin counts.
  • the optimization hints 1134 can indicate that the time slots 1106 are not enough to provide sufficient time to perform the optimization procedure 934 .
  • the optimization hints 1134 can indicate that the application 304 cannot be partitioned with a number of the application fragments 946 less than the maximum fragment number.
  • the evaluation module 1136 can be implemented with a factor profile generator 1140 in the schedule formation unit 1104 for updating the factor profile 1108 based on the evaluation module 1136 evaluated by the schedule manager 1138 . If the optimization result 1130 indicates a success, the factor profile 1108 is not updated and thus the optimization procedure 934 can proceed based on the reservation tables 1132 .
  • the factor profile generator 1140 updates the factor profile 1108 .
  • the factor profile 1108 can be updated based on the optimization hints 1134 .
  • the factor profile 1108 can be updated with parameters within constraints of limits specified by configuration registers 1142 in the schedule formation unit 1104 .
  • the configuration registers 1142 include parametric settings specific to each of the time slots 1106 that are used by the optimization procedure 934 .
  • the optimization procedure 934 is rescheduled to be performed with a new set of the parameters.
  • the optimization procedure 934 can be rescheduled by the scenario formulation unit 1114 restarted to perform the optimization procedure 934 again.
  • the reservation tables 1132 can be used as a stable configuration of the microkernel resources 936 and the reconfigurable resources 930 .
  • the reservation tables 1132 can be valid for a number of the time slots 1106 .
  • the optimization procedure 934 can be performed in a distributed manner.
  • the first user interface unit 910 in the first microkernel 908 can send the user request 926 of FIG. 9 to the second user interface unit 920 in the second microkernel 918 .
  • the first microkernel 908 can establish the login session 1006 to perform the optimization procedure 934 using the microkernel resources 936 and the reconfigurable resources 930 in the second microkernel 918 for the second fragment 952 .
  • the user request 926 can include information from the factor profile 1108 so that the second microkernel 918 can used as a starting point for the optimization procedure 934 . If the second microkernel 918 cannot perform the optimization procedure 934 with the factor profile 1108 provided by the first microkernel 908 , the second microkernel 918 can provide the optimization hints 1134 back to the first microkernel 908 .
  • the second microkernel 918 can save the optimization result 1130 using another of the reservation tables 1132 stored in the second database 1122 .
  • the second microkernel 918 can notify the first microkernel 908 regarding completion of the optimization procedure 934 performed in the second microkernel 918 .
  • the first microkernel 908 can subsequently communicate with the second microkernel 918 to retrieve information from the second database 1122 to obtain the optimization result 1130 .
  • Inter-cluster communication between the first fragment 948 in the first cluster 904 and the second fragment 952 in the second cluster 914 can be provided using a set of switch complex commands sent through the intra-cluster communication unit 718 of FIG. 7 and the inter-cluster communication unit 728 of FIG. 7 .
  • the switch complex commands provide a mechanism to control data traffic through the switch fabric 724 .
  • the switch complex commands provide information for routing, signal buffer configuration, virtual bus configuration, and alarm management.
  • the optimization module 1112 can generate and send an agent command 1144 from the first microkernel 908 to the second microkernel 918 .
  • the agent command 1144 provides control of the microkernel resources 936 , the reconfigurable resources 930 , or a combination thereof for the implementation of the application fragments 946 .
  • the agent command 1144 can be generated by the application agent 1014 of FIG. 10 of the first microkernel 908 .
  • the agent command 1144 can be sent from the first user interface unit 910 to the second user interface unit 920 .
  • the agent command 1144 can include a start machine/process command, a halt machine/process command, and a resume machine/process command.
  • the agent command 1144 can include a restart machine/process command, a dissolve machine/process command, an update machine/process factors command, and a change machine/process priority command.
  • a machine is defined as a physical instance of a logic transformation pipeline.
  • a pipeline is defined as a set of circuitry residing within an instance of the clusters 404 , including the reconfigurable hardware devices 202 , used to implement the application 304 or a portion thereof.
  • the machine can include a hardware circuitry making up the pipeline or various fragments of circuits, data connections including switches, or a combination thereof.
  • the start machine/process command initiates the application 304 with an application identifier (ID) using a factor template with incremental adjustments in a factor list.
  • the factor list can include parameter/value pairs. Placement can be limited to a location list.
  • the halt machine/process command stalls a machine/process tagged with a machine/process ID.
  • a state of data flowing through a machine/process can freeze. No data can enter or leave an affected machine on behalf of a process, and intermediate data can remain unchanged and in place.
  • the resume machine/process command unfreezes a stalled machine/process tagged with a machine/process ID.
  • data can flow through a machine/process and intermediate data associated with the machine can be allowed to change state.
  • the restart machine/process command resets a machine/process tagged with a machine/process ID.
  • the start machine/process command can include emptying a pipeline and resuming processing inputs starting with the next data in queues feeding input virtual buses.
  • the update machine/process factors command changes system parametric values associated with a machine/process tagged with a machine/process ID. Factors are detailed in a factor list, which can include parameter/value pairs.
  • the change machine/process priority command changes a priority associated with a machine/process tagged with a machine/process ID to a new priority.
  • the optimization module 1112 can send a dispatcher command 1146 from the first microkernel 908 to the second microkernel 918 .
  • the dispatcher command 1146 is a high-level command for controlling programming of the first reconfigurable hardware devices 912 and the second reconfigurable hardware devices 922 .
  • the dispatcher command 1146 can be sent from the first user interface unit 910 to the second user interface unit 920 .
  • the dispatcher command 1146 can include the high-level command including an instantiate machine fragment command, a dissolve machine fragment command, a pump machine fragment command, and a siphon machine fragment command.
  • the dispatcher command 1146 can include the high-level command including a verify machine command, a form connection command, a dissolve connection command, a merge stream command, and a split stream command.
  • the siphon machine fragment command prepares the second fragment 952 for removal by streaming application state out of the second fragment 952 and into an indicated table row.
  • This command can include direct memory access evacuation and buffering of indicated embedded instances of the memory devices 726 .
  • the verify machine command performs a checksum on the programming of the second reconfigurable hardware devices 922 and verifies the checksum against a stored value collected at synthesis or upon completion of the optimization procedure 934 .
  • the checksum is defined as fixed-sized information used for detecting errors in data that can be introduced during transmission or storage of the data.
  • the form connection command attaches application nodes to a trans-core interconnect by configuring interconnect sectors in the second reconfigurable hardware devices 922 .
  • the dissolve connection command detaches application nodes from a trans-core interconnect by returning appropriate interconnect sectors to a reset state.
  • the merge stream command adds a tagged signal to multiplex feeding a threaded machine, which is a hardware resource that is capable of implementing multiple threads of operation.
  • the split stream command removes a tagged signal from multiplex feeding the threaded machine.
  • the specification module 1102 or the optimization module 1112 can send a connection command 1148 .
  • the connection command 1148 can be sent from the communication manager of the resource manager 714 in the first microkernel 908 to a second application agent 1150 of another of the resource manager 714 in the second microkernel 918 .
  • the connection command 1148 opens or closes individual connections between the first microkernel 908 to the second microkernel 918 .
  • the connection command 1148 can be sent from the first user interface unit 910 to the second user interface unit 920 .
  • the connection command 1148 can include an open connection command, a close connection command, an activate connection command, a suspend connection command, and a bridge connection command.
  • the connection command 1148 can include a modify connection command, a form channel command, a close channel command, and an activate channel suspend channel.
  • the open connection command opens a connection from the first kernel unit 906 to each member of a destination list with a respective protocol.
  • the destination list can include the second kernel unit 916 or any other instances of the clusters 404 .
  • Either a connection identifier or an error code can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 .
  • the activate connection command activates a connection from a suspended state that is attached to the first kernel unit 906 and labeled with a connection ID.
  • An error code can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 .
  • the form channel command is associated with a collection of connections in connection ID list for group operations.
  • Options associated with the form channel command can include an assignment of a channel to a virtual bus. If the channel is assigned to the virtual bus, backpressure and enable port numbers can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 . Otherwise, an error code can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 .
  • the close channel command closes all connections in a channel group from the first kernel unit 906 labeled with a channel ID, and then returns a channel descriptor and an identifier for reuse.
  • An error code can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 .
  • the activate channel activates a channel from a suspended state that is attached to the first kernel unit 906 and labeled with a channel ID.
  • An error code can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 .
  • the suspend channel suspends a channel from an active state that is attached to the first kernel unit 906 and labeled with a channel ID.
  • An error code can be returned from the second application agent 1150 to the communication manager in the first kernel unit 906 .
  • the slack capacity 1124 provides improved performance because the slack capacity 1124 provides additional instances of the microkernel resources 936 and the reconfigurable resources 930 in the second cluster 914 for implementing and simultaneously implementing the application fragments 946 resulting in reduced execution time of the application 304 .
  • the second cluster 914 connected to the first cluster 904 provides improved availability of free resources for implementing the application 304 since the first microkernel 908 is able to communicate with the second microkernel 918 to access the second database 1122 through the communication network 502 and the communication interface 504 .
  • the optimization module 1112 of FIG. 11 can include a method of implementing or fitting the application 304 of FIG. 3 to free sectors available in the first reconfigurable hardware devices 912 of FIG. 9 , the second reconfigurable hardware devices 922 of FIG. 9 , or a combination thereof.
  • the search module 1128 can expand a search domain.
  • the search domain can be expanded into multiple of the time slots 1106 of FIG. 11 implying the application 304 that can be spread across more than multiple of the time slots 1106 .
  • an error status can be set or registered.
  • the error flag can set or signal an event. Otherwise, a stack of resource lists for the time slots 1106 is cycled.
  • the optimization procedure 934 of FIG. 9 can work through each of the resource lists.
  • the search module 1128 can expand the search domain for the reconfigurable resources 930 across the first cluster 904 of FIG. 9 and the second cluster 914 of FIG. 9 .
  • the reconfigurable resources 930 can be searched for in order to implement the application 304 .
  • the search module 1128 can start a search based on a multi-plane scope 1202 and a target scope 1204 .
  • the multi-plane scope 1202 indicates whether the search is performed not only in the first cluster 904 but also in the second cluster 914 .
  • the target scope 1204 indicates whether the search is performed to find instances of the first reconfigurable hardware devices 912 that are available for implementation of the application fragments 946 of FIG. 9 .
  • the multi-plane scope 1202 and the target scope 1204 can be configured to a known state or assigned to a fixed state in the optimization module 1112 .
  • the search module 1128 can include a flunk check module 1206 to fail a resource check. If the multi-plane scope 1202 is “yes” indicating that the search has been performed in the second cluster 914 , the flunk check module 1206 can fail the resource check since the resource check cannot find any of the reconfigurable resources 930 that are available.
  • the shift-to-plane-list module 1208 can search each of the kernel plane lists 1210 for the available sectors in the first reconfigurable hardware devices 912 .
  • the shift-to-plane-list module 1208 can search the kernel plane lists 1210 to find or search for the available sectors that fit the functionality of the application fragments 946 to implement the application fragments 946 .
  • the search module 1128 can include a shift-to-multiplane-list module 1212 to cycle or search through multiplane lists 1214 to search for the available instances of the reconfigurable resources 930 .
  • the multiplane lists 1214 are collections of instances of the second reconfigurable hardware devices 922 that have available sectors for implementation of the application fragments 946 .
  • the multiplane lists 1214 can include portions of the second database 1122 of FIG. 11 including the available sectors in the instances of the second reconfigurable hardware devices 922 .
  • the shift-to-multiplane-list module 1212 can search each of the multiplane lists 1214 for the available sectors in the second reconfigurable hardware devices 922 .
  • the shift-to-multiplane-list module 1212 can search the multiplane lists 1214 to find or search for the available sectors that fit the functionality of the application fragments 946 to implement the application fragments 946 .
  • the search module 1128 can assert or indicate that the search ends.
  • the available sectors can be included or reserved in the reservation tables 1132 of FIG. 11 .
  • the search module 1128 can confirm that the reservation tables 1132 are ready for use.
  • the search module 1128 can include a resynchronize module 1216 to obtain an updated copy of the multiplane lists 1214 in order for the shift-to-multiplane-list module 1212 can be performed again. If the available sectors cannot be reserved to implement the application fragments 946 , the resynchronize module 1216 can resynchronize to get an update of the multiplane lists 1214 . The shift-to-multiplane-list module 1212 can get the update of the multiplane lists 1214 and perform its search again.
  • the search module 1128 effectively improves the search for the reconfigurable resources 930 by performing the search using the shift-to-multiplane-list module 1212 and the resynchronize module 1216 in addition to the shift-to-plane-list module 1208 resulting in detection of the available sectors for implementing the application fragments 946 .
  • the computing system 100 of FIG. 1 describes the module functions or order as an example.
  • the modules can be partitioned differently.
  • Each of the modules can operate individually and independently of the other modules.
  • the analyze module 1010 of FIG. 10 and the launch module 1012 of FIG. 10 can be implemented in one module instead of two different modules.
  • the method 1300 includes: providing a first cluster having a first kernel unit for managing a first reconfigurable hardware device in a block 1302 ; analyzing an application descriptor associated with an application in a block 1304 ; generating a first bitstream based on the application descriptor for loading the first reconfigurable hardware device, the first bitstream for implementing at least a first portion of the application in a block 1306 ; and implementing a first fragment with the first bitstream in the first cluster in a block 1308 .
  • the computing system of the present invention furnishes important and heretofore unknown and unavailable solutions, capabilities, and functional aspects for a computing system with hardware reconfiguration mechanism.
  • the resulting method, process, apparatus, device, product, and/or system is straightforward, cost-effective, uncomplicated, highly versatile, accurate, sensitive, and effective, and can be implemented by adapting known components for ready, efficient, and economical manufacturing, application, and utilization.
  • Another important aspect of the present invention is that it valuably supports and services the historical trend of reducing costs, simplifying systems, and increasing performance.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Computing Systems (AREA)
  • Environmental & Geological Engineering (AREA)
  • Evolutionary Computation (AREA)
  • Geometry (AREA)
  • Software Systems (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Quality & Reliability (AREA)
  • Logic Circuits (AREA)
  • Stored Programmes (AREA)
  • Design And Manufacture Of Integrated Circuits (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US13/464,627 2011-05-06 2012-05-04 Computing system with hardware reconfiguration mechanism and method of operation thereof Abandoned US20120284501A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/464,627 US20120284501A1 (en) 2011-05-06 2012-05-04 Computing system with hardware reconfiguration mechanism and method of operation thereof
US16/297,431 US11494322B2 (en) 2011-05-06 2019-03-08 Computing system with hardware reconfiguration mechanism and method of operation thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161483523P 2011-05-06 2011-05-06
US13/464,627 US20120284501A1 (en) 2011-05-06 2012-05-04 Computing system with hardware reconfiguration mechanism and method of operation thereof

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/297,431 Continuation US11494322B2 (en) 2011-05-06 2019-03-08 Computing system with hardware reconfiguration mechanism and method of operation thereof

Publications (1)

Publication Number Publication Date
US20120284501A1 true US20120284501A1 (en) 2012-11-08

Family

ID=47091004

Family Applications (8)

Application Number Title Priority Date Filing Date
US13/464,627 Abandoned US20120284501A1 (en) 2011-05-06 2012-05-04 Computing system with hardware reconfiguration mechanism and method of operation thereof
US13/464,836 Active 2033-01-08 US8868894B2 (en) 2011-05-06 2012-05-04 Computing system with hardware scheduled reconfiguration mechanism and method of operation thereof
US13/464,722 Active 2033-04-30 US8869087B2 (en) 2011-05-06 2012-05-04 Computing system with data and control planes and method of operation thereof
US13/464,873 Active US8756548B2 (en) 2011-05-06 2012-05-04 Computing system with hardware reconfiguration mechanism and method of operation thereof
US13/464,892 Active 2033-04-04 US9152748B2 (en) 2011-05-06 2012-05-04 Computing system with switching mechanism and method of operation thereof
US13/465,955 Active 2033-05-19 US9053266B2 (en) 2011-05-06 2012-05-07 Computing system with hardware bus management and method of operation thereof
US14/702,527 Active 2032-05-10 US9495310B2 (en) 2011-05-06 2015-05-01 Computing system with hardware bus management and method of operation thereof
US16/297,431 Active US11494322B2 (en) 2011-05-06 2019-03-08 Computing system with hardware reconfiguration mechanism and method of operation thereof

Family Applications After (7)

Application Number Title Priority Date Filing Date
US13/464,836 Active 2033-01-08 US8868894B2 (en) 2011-05-06 2012-05-04 Computing system with hardware scheduled reconfiguration mechanism and method of operation thereof
US13/464,722 Active 2033-04-30 US8869087B2 (en) 2011-05-06 2012-05-04 Computing system with data and control planes and method of operation thereof
US13/464,873 Active US8756548B2 (en) 2011-05-06 2012-05-04 Computing system with hardware reconfiguration mechanism and method of operation thereof
US13/464,892 Active 2033-04-04 US9152748B2 (en) 2011-05-06 2012-05-04 Computing system with switching mechanism and method of operation thereof
US13/465,955 Active 2033-05-19 US9053266B2 (en) 2011-05-06 2012-05-07 Computing system with hardware bus management and method of operation thereof
US14/702,527 Active 2032-05-10 US9495310B2 (en) 2011-05-06 2015-05-01 Computing system with hardware bus management and method of operation thereof
US16/297,431 Active US11494322B2 (en) 2011-05-06 2019-03-08 Computing system with hardware reconfiguration mechanism and method of operation thereof

Country Status (2)

Country Link
US (8) US20120284501A1 (fr)
WO (5) WO2012154586A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120284439A1 (en) * 2011-05-06 2012-11-08 Xcelemor, Inc. Computing system with hardware bus management and method of operation thereof
US20160063226A1 (en) * 2014-09-03 2016-03-03 Microsoft Corporation Shared Session Techniques
US20160321081A1 (en) * 2015-05-02 2016-11-03 Hyeung-Yun Kim Embedded systems of internet-of-things incorporating a cloud computing service of FPGA reconfiguration
US10558437B1 (en) * 2013-01-22 2020-02-11 Altera Corporation Method and apparatus for performing profile guided optimization for high-level synthesis
US10608641B2 (en) 2018-07-20 2020-03-31 Xilinx, Inc. Hierarchical partial reconfiguration for programmable integrated circuits
US10621299B1 (en) * 2018-02-05 2020-04-14 Xilinx, Inc. Dynamic platform support in programmable integrated circuits
US10891414B2 (en) * 2019-05-23 2021-01-12 Xilinx, Inc. Hardware-software design flow for heterogeneous and programmable devices
US10977018B1 (en) 2019-12-05 2021-04-13 Xilinx, Inc. Development environment for heterogeneous devices
US20210255897A1 (en) * 2017-09-29 2021-08-19 Intel Corporation Technologies for opportunistic acceleration overprovisioning for disaggregated architectures
US11188312B2 (en) 2019-05-23 2021-11-30 Xilinx, Inc. Hardware-software design flow with high-level synthesis for heterogeneous and programmable devices
US11301295B1 (en) 2019-05-23 2022-04-12 Xilinx, Inc. Implementing an application specified as a data flow graph in an array of data processing engines
US11886789B1 (en) 2021-07-07 2024-01-30 Xilinx, Inc. Block design containers for circuit design

Families Citing this family (50)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8789065B2 (en) 2012-06-08 2014-07-22 Throughputer, Inc. System and method for input data load adaptive parallel processing
WO2012149474A2 (fr) 2011-04-28 2012-11-01 Zoll Circulation, Inc. Distribution virale de paramètres de gestion de batterie
JP6195558B2 (ja) * 2011-04-28 2017-09-13 ゾール サーキュレイション インコーポレイテッドＺＯＬＬ Ｃｉｒｃｕｌａｔｉｏｎ，Ｉｎｃ． バッテリー性能データを追跡および保管するためのシステムおよび方法
US9448847B2 (en) 2011-07-15 2016-09-20 Throughputer, Inc. Concurrent program execution optimization
WO2013020001A1 (fr) * 2011-08-02 2013-02-07 Cavium, Inc. Processeur de sortie d'un frontal de recherche
US9247512B2 (en) * 2011-08-25 2016-01-26 Ubiquiti Networks Adaptive synchronous protocol for minimizing latency in TDD systems
US9237169B2 (en) * 2012-06-01 2016-01-12 Apple Inc. Network stream identification for open FaceTime
US10104447B2 (en) * 2012-06-19 2018-10-16 Saturn Licensing Llc Extensions to trigger parameters table for interactive television
KR20140054948A (ko) * 2012-10-30 2014-05-09 한국전자통신연구원 임베디드 시스템을 위한 오픈씨엘 응용 소프트웨어 개발 지원 도구 구성 및 방법
US9253077B2 (en) * 2012-11-30 2016-02-02 International Business Machines Corporation Parallel top-K simple shortest paths discovery
US9095221B1 (en) 2013-02-20 2015-08-04 Tiffany & Tiffany Designer, Inc. Convertible furniture with selectively expandable mattress cushion section(s)
US9276846B2 (en) 2013-03-15 2016-03-01 Cavium, Inc. Packet extraction optimization in a network processor
US20140282022A1 (en) * 2013-03-15 2014-09-18 Miselu Inc Configuring device layouts
US9817933B2 (en) * 2013-03-15 2017-11-14 The Regents Of The University Of California Systems and methods for switching using hierarchical networks
US9275168B2 (en) 2013-07-19 2016-03-01 International Business Machines Corporation Hardware projection of fixed and variable length columns of database tables
US9235564B2 (en) 2013-07-19 2016-01-12 International Business Machines Corporation Offloading projection of fixed and variable length database columns
WO2015034751A1 (fr) * 2013-09-05 2015-03-12 Franklin Electric Co., Inc. Système et procédé de commande de moteur
GB2526018B (en) * 2013-10-31 2018-11-14 Silicon Tailor Ltd Multistage switch
US9781495B2 (en) * 2014-08-14 2017-10-03 Huawei Technologies Co., Ltd. Optical switch architecture
US9515658B1 (en) * 2014-10-09 2016-12-06 Altera Corporation Method and apparatus for implementing configurable streaming networks
US10015048B2 (en) 2014-12-27 2018-07-03 Intel Corporation Programmable protocol parser for NIC classification and queue assignments
EP3975429A1 (fr) 2015-02-22 2022-03-30 Flex Logix Technologies, Inc. Architecture et circuit intégré de matrice de commutateur à la base mixte et/ou en mode mixte
US9826071B2 (en) 2015-08-26 2017-11-21 Barefoot Networks, Inc. Configuring a switch for extracting packet header fields
US9825862B2 (en) 2015-08-26 2017-11-21 Barefoot Networks, Inc. Packet header field extraction
US9984194B2 (en) * 2015-09-15 2018-05-29 Arm Limited Integrated circuit design
US9912774B2 (en) 2015-12-22 2018-03-06 Intel Corporation Accelerated network packet processing
CN105718421B (zh) * 2016-01-25 2019-03-01 东南大学 一种面向多个粗粒度动态可重构阵列的数据缓存更新系统
US10063407B1 (en) 2016-02-08 2018-08-28 Barefoot Networks, Inc. Identifying and marking failed egress links in data plane
US9949133B2 (en) * 2016-08-05 2018-04-17 Nxgen Partners Ip, Llc Ultra-broadband virtualized telecom and internet
US10757576B2 (en) 2016-08-05 2020-08-25 Nxgen Partners Ip, Llc SDR-based massive MIMO with V-RAN cloud architecture and SDN-based network slicing
US10932142B2 (en) 2017-01-09 2021-02-23 Nxgen Partners Ip, Llc Point-to-multipoint or multipoint-to-multipoint mesh self-organized network over WiGig standards with new MAC layer
CN106919418B (zh) * 2017-01-22 2020-11-27 北京奇艺世纪科技有限公司 在线应用快速回滚的方法及装置
US10419366B1 (en) * 2017-01-31 2019-09-17 Barefoot Networks, Inc. Mechanism for communicating to remote control plane from forwarding element
CN106776372B (zh) * 2017-02-15 2019-09-24 北京中航通用科技有限公司 基于fpga的仿真数据存取方法及装置
CN107025203B (zh) * 2017-03-31 2020-09-25 新华三技术有限公司 第一板卡、第二板卡及一种设备
US10694006B1 (en) 2017-04-23 2020-06-23 Barefoot Networks, Inc. Generation of descriptive data for packet fields
CN109117253B (zh) * 2017-06-26 2022-05-24 阿里巴巴集团控股有限公司 一种微内核调度的方法和装置
US11503141B1 (en) 2017-07-23 2022-11-15 Barefoot Networks, Inc. Stateful processing unit with min/max capability
KR102668340B1 (ko) 2017-08-03 2024-05-22 넥스트 실리콘 리미티드 설정가능한 하드웨어 런타임 최적화
WO2019055675A1 (fr) * 2017-09-13 2019-03-21 Next Silicon, Ltd. Architecture de flux de données à grille dirigée et interconnectée
US10771387B1 (en) 2017-09-28 2020-09-08 Barefoot Networks, Inc. Multiple packet data container types for a processing pipeline
US11113442B2 (en) * 2017-09-28 2021-09-07 Intel Corporation Methods and apparatus for reducing reliability degradation on an integrated circuit
KR102409505B1 (ko) * 2017-12-22 2022-06-14 에스케이하이닉스 주식회사 비휘발성 메모리 소자를 포함하는 lut, lut를 포함하는 fpga 및 fpga 디자인 방법
WO2020086053A1 (fr) * 2018-10-22 2020-04-30 Mentor Graphics Corporation Attribution dynamique de ressources de calcul pour des opérations d'automatisation de conception électronique
KR20250095753A (ko) * 2019-08-22 2025-06-26 구글 엘엘씨 온칩 오퍼레이션 초기화
EP4085354A4 (fr) * 2019-12-30 2024-03-13 Star Ally International Limited Processeur pour calculs parallèles configurables
US11152991B2 (en) 2020-01-23 2021-10-19 Nxgen Partners Ip, Llc Hybrid digital-analog mmwave repeater/relay with full duplex
US11269526B2 (en) 2020-04-23 2022-03-08 Next Silicon Ltd Interconnected memory grid with bypassable units
US11182325B1 (en) * 2020-06-01 2021-11-23 Smart Modular Technologies, Inc. Memory centric computing storage controller system
US11722435B2 (en) * 2021-11-18 2023-08-08 United States Of America As Represented By The Secretary Of The Navy System with layer-one switch for flexible communication interconnections

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040049672A1 (en) * 2002-05-31 2004-03-11 Vincent Nollet System and method for hardware-software multitasking on a reconfigurable computing platform
US20050097485A1 (en) * 2003-10-29 2005-05-05 Guenthner Russell W. Method for improving performance of critical path in field programmable gate arrays
US20060003757A1 (en) * 2000-01-28 2006-01-05 Infineon Technologies Ag Wireless spread spectrum communication platform using dynamically reconfigurable logic
US20070201380A1 (en) * 2006-02-24 2007-08-30 Cisco Technology, Inc. Method and system for power-efficient adaptive link aggregation

Family Cites Families (79)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0410502B1 (fr) 1989-07-27 1997-05-28 Lsi Logic Corporation Méthode et appareil pour émuler l'interaction entre un circuit intégré d'application spécifique (ASIC) en développement et un système de destination
JP3737104B2 (ja) * 1992-06-04 2006-01-18 ジリンクス，インコーポレーテッド プログラム可能な集積回路デバイスにユーザ回路を配置するタイミング駆動式の方法
US5761484A (en) * 1994-04-01 1998-06-02 Massachusetts Institute Of Technology Virtual interconnections for reconfigurable logic systems
US5838908A (en) * 1994-11-14 1998-11-17 Texas Instruments Incorporated Device for having processors each having interface for transferring delivery units specifying direction and distance and operable to emulate plurality of field programmable gate arrays
US5659716A (en) * 1994-11-23 1997-08-19 Virtual Machine Works, Inc. Pipe-lined static router and scheduler for configurable logic system performing simultaneous communications and computation
US6097211A (en) 1996-07-18 2000-08-01 Altera Corporation Configuration memory integrated circuit
US6421817B1 (en) * 1997-05-29 2002-07-16 Xilinx, Inc. System and method of computation in a programmable logic device using virtual instructions
US5960191A (en) * 1997-05-30 1999-09-28 Quickturn Design Systems, Inc. Emulation system with time-multiplexed interconnect
US6784903B2 (en) * 1997-08-18 2004-08-31 National Instruments Corporation System and method for configuring an instrument to perform measurement functions utilizing conversion of graphical programs into hardware implementations
US6470415B1 (en) 1999-10-13 2002-10-22 Alacritech, Inc. Queue system involving SRAM head, SRAM tail and DRAM body
US6697868B2 (en) 2000-02-28 2004-02-24 Alacritech, Inc. Protocol processing stack for use with intelligent network interface device
US6434687B1 (en) 1997-12-17 2002-08-13 Src Computers, Inc. System and method for accelerating web site access and processing utilizing a computer system incorporating reconfigurable processors operating under a single operating system image
US6099583A (en) * 1998-04-08 2000-08-08 Xilinx, Inc. Core-based placement and annealing methods for programmable logic devices
US6086631A (en) * 1998-04-08 2000-07-11 Xilinx, Inc. Post-placement residual overlap removal method for core-based PLD programming process
US6314501B1 (en) 1998-07-23 2001-11-06 Unisys Corporation Computer system and method for operating multiple operating systems in different partitions of the computer system and for allowing the different partitions to communicate with one another through shared memory
US6292916B1 (en) 1998-12-10 2001-09-18 Lucent Technologies Inc. Parallel backtracing for satisfiability on reconfigurable hardware
US6539438B1 (en) * 1999-01-15 2003-03-25 Quickflex Inc. Reconfigurable computing system and method and apparatus employing same
US6442732B1 (en) 1999-04-21 2002-08-27 Lucent Technologies, Inc. Virtual logic system for solving satisfiability problems using reconfigurable hardware
US6519754B1 (en) * 1999-05-17 2003-02-11 Synplicity, Inc. Methods and apparatuses for designing integrated circuits
FR2794876B1 (fr) * 1999-06-10 2001-11-02 Bull Sa Procede de reconfiguration d'un systeme de traitement de l'information sur detection de defaillance d'un composant
US7301941B2 (en) * 2000-04-11 2007-11-27 Lsi Corporation Multistage digital cross connect with synchronized configuration switching
US7379859B2 (en) * 2001-04-24 2008-05-27 Mentor Graphics Corporation Emulator with switching network connections
US6751723B1 (en) * 2000-09-02 2004-06-15 Actel Corporation Field programmable gate array and microcontroller system-on-a-chip
US20020072893A1 (en) * 2000-10-12 2002-06-13 Alex Wilson System, method and article of manufacture for using a microprocessor emulation in a hardware application with non time-critical functions
US6990649B2 (en) * 2001-03-21 2006-01-24 John Claras Method to configure and quote component arrays
US7047464B2 (en) * 2001-12-10 2006-05-16 International Business Machines Corporation Method and system for use of a field programmable function within an application specific integrated circuit (ASIC) to access internal signals for external observation and control
US6914902B2 (en) * 2002-04-16 2005-07-05 Opal Acquisition Corporation Distributed semi-rearrangeable non-blocking algorithm for clos networks
US7073158B2 (en) * 2002-05-17 2006-07-04 Pixel Velocity, Inc. Automated system for designing and developing field programmable gate arrays
US7310333B1 (en) * 2002-06-28 2007-12-18 Ciena Corporation Switching control mechanism for supporting reconfiguaration without invoking a rearrangement algorithm
US7028281B1 (en) * 2002-07-12 2006-04-11 Lattice Semiconductor Corporation FPGA with register-intensive architecture
US6941539B2 (en) 2002-10-31 2005-09-06 Src Computers, Inc. Efficiency of reconfigurable hardware
US7155708B2 (en) 2002-10-31 2006-12-26 Src Computers, Inc. Debugging and performance profiling using control-dataflow graph representations with reconfigurable hardware emulation
US6964029B2 (en) 2002-10-31 2005-11-08 Src Computers, Inc. System and method for partitioning control-dataflow graph representations
US7185299B1 (en) * 2003-01-30 2007-02-27 Xilinx, Inc. Methods of estimating routing delays during the placement process in programmable logic devices
JP2004234530A (ja) 2003-01-31 2004-08-19 Fujitsu Ten Ltd マイクロコンピュータのロジック開発装置
US6930510B2 (en) * 2003-03-03 2005-08-16 Xilinx, Inc. FPGA architecture with mixed interconnect resources optimized for fast and low-power routing and methods of utilizing the same
US8639487B1 (en) * 2003-03-25 2014-01-28 Cadence Design Systems, Inc. Method for multiple processor system-on-a-chip hardware and software cogeneration
US7120571B2 (en) * 2003-06-16 2006-10-10 Fortelink, Inc. Resource board for emulation system
US7366652B2 (en) * 2003-06-16 2008-04-29 Springsoft, Inc. Method of programming a co-verification system
US7013449B2 (en) * 2003-10-30 2006-03-14 Hewlett-Packard Development Company, L.P. Method of designing custom circuit device using scheduling clock cycles
US7120706B2 (en) * 2003-10-31 2006-10-10 Lucent Technologies Inc. Contention resolution in a memory management system
US7159049B2 (en) 2003-10-31 2007-01-02 Lucent Technologies Inc. Memory management system including on access flow regulator for a data processing system
US7162551B2 (en) 2003-10-31 2007-01-09 Lucent Technologies Inc. Memory management system having a linked list processor
US7251803B2 (en) * 2003-11-05 2007-07-31 Peter Ramyalal Suaris Memory re-implementation for field programmable gate arrays
US7669035B2 (en) * 2004-01-21 2010-02-23 The Charles Stark Draper Laboratory, Inc. Systems and methods for reconfigurable computing
WO2005119532A2 (fr) * 2004-06-04 2005-12-15 The Regents Of The University Of California Circuits fpga a faible puissance et procedes associes
US7506297B2 (en) * 2004-06-15 2009-03-17 University Of North Carolina At Charlotte Methodology for scheduling, partitioning and mapping computational tasks onto scalable, high performance, hybrid FPGA networks
EP1615141B1 (fr) 2004-07-01 2018-03-07 Harman Becker Automotive Systems GmbH Architecture d'ordinateur pour un système multimedia mobile utilisé dans un véhicule
US8098676B2 (en) 2004-08-12 2012-01-17 Intel Corporation Techniques to utilize queues for network interface devices
US7231623B2 (en) * 2004-09-30 2007-06-12 Lsi Corporation Netlist database
US7752588B2 (en) * 2005-06-29 2010-07-06 Subhasis Bose Timing driven force directed placement flow
US8949364B2 (en) * 2005-09-15 2015-02-03 Ca, Inc. Apparatus, method and system for rapid delivery of distributed applications
US20070096876A1 (en) * 2005-10-20 2007-05-03 Raj Bridgelall Adaptive RFID devices
US7454658B1 (en) * 2006-02-10 2008-11-18 Xilinx, Inc. In-system signal analysis using a programmable logic device
US7873930B2 (en) * 2006-03-24 2011-01-18 Synopsys, Inc. Methods and systems for optimizing designs of integrated circuits
US8645955B2 (en) * 2006-06-12 2014-02-04 Samsung Electronics Co., Ltd. Multitasking method and apparatus for reconfigurable array
US7571414B2 (en) * 2006-06-15 2009-08-04 National Chip Implementation Center, National Applied Research Laboratories Multi-project system-on-chip and its method
WO2007149495A2 (fr) * 2006-06-21 2007-12-27 Element Cxi, Llc Système d'association de programmes et procédé et logiciel pour architecture de circuit intégré souple
US20080086575A1 (en) 2006-10-06 2008-04-10 Annie Foong Network interface techniques
US20080148277A1 (en) * 2006-12-18 2008-06-19 Nokia Corporation Optimizing calls from a managed runtime environment to microkernel extended functionality
US20080184241A1 (en) * 2007-01-30 2008-07-31 Microsoft Corporation Techniques for automated balancing of tasks across multiple computers
GB2446455B (en) * 2007-02-08 2011-08-17 Adder Tech Ltd Video switch and method of sampling simultaneous video sources
JP2008226181A (ja) * 2007-03-15 2008-09-25 Fujitsu Ltd 並列実行プログラム、該プログラムを記録した記録媒体、並列実行装置および並列実行方法
US7831943B1 (en) * 2007-04-16 2010-11-09 Xilinx, Inc. Checking for valid slice packing in a programmable device
US20080276252A1 (en) * 2007-05-04 2008-11-06 Microsoft Corporation Kernel event visualization
WO2009018855A1 (fr) * 2007-08-06 2009-02-12 Telefonaktiebolaget Lm Ericsson (Publ) Matrice de commutation et procédé de spécification de matrice de commutation
US7734948B2 (en) * 2007-08-21 2010-06-08 International Business Machines Corporation Recovery of a redundant node controller in a computer system
US8018249B2 (en) * 2007-09-13 2011-09-13 Friedrich-Alexander-Universitaet-Erlangen-Nuernberg Logic chip, logic system and method for designing a logic chip
WO2009088435A1 (fr) * 2007-12-31 2009-07-16 Netapp, Inc. Système et procédé pour un équilibrage de charge de stockage automatique dans des environnements de serveurs virtuels
US20100274550A1 (en) * 2008-01-24 2010-10-28 National Chung Cheng University Integrated development structure having virtual inputs/outputs for embedded hardware/software
US20090276527A1 (en) 2008-05-02 2009-11-05 Mcclain John Wesley Ferguson Light Weight Process Abstraction For Distributed Systems
US7962665B2 (en) 2008-09-26 2011-06-14 International Business Machines Corporation Managing condition indicators that use the same physical indicator device in a logically partitioned computer system
US9104435B2 (en) * 2009-04-14 2015-08-11 Empire Technology Development Llc Program and data annotation for hardware customization and energy optimization
US8589600B2 (en) 2009-12-14 2013-11-19 Maxeler Technologies, Ltd. Method of transferring data with offsets
US8805914B2 (en) 2010-06-02 2014-08-12 Maxeler Technologies Ltd. Method and apparatus for performing numerical calculations
US8336017B2 (en) * 2011-01-19 2012-12-18 Algotochip Corporation Architecture optimizer
WO2012154586A1 (fr) 2011-05-06 2012-11-15 Xcelemor, Inc. Système informatique à mécanisme de reconfiguration matérielle et son procédé d'exploitation
US9055069B2 (en) * 2012-03-19 2015-06-09 Xcelemor, Inc. Hardware computing system with software mediation and method of operation thereof
US9026688B2 (en) * 2012-06-21 2015-05-05 Breakingpoint Systems, Inc. Systems and methods for programming configurable logic devices via USB

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060003757A1 (en) * 2000-01-28 2006-01-05 Infineon Technologies Ag Wireless spread spectrum communication platform using dynamically reconfigurable logic
US20040049672A1 (en) * 2002-05-31 2004-03-11 Vincent Nollet System and method for hardware-software multitasking on a reconfigurable computing platform
US20050097485A1 (en) * 2003-10-29 2005-05-05 Guenthner Russell W. Method for improving performance of critical path in field programmable gate arrays
US20070201380A1 (en) * 2006-02-24 2007-08-30 Cisco Technology, Inc. Method and system for power-efficient adaptive link aggregation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Kao et al., "A Sequential Circuit Partitioning Algorithm for Dynamically Reconfigurable FPGAs", International Conference on Communication, Circuits and Systems", July 11, 2007, Pages 1185-1188, Publisher: ICCCAS *

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9053266B2 (en) * 2011-05-06 2015-06-09 Xcelemor, Inc. Computing system with hardware bus management and method of operation thereof
US9495310B2 (en) 2011-05-06 2016-11-15 Xcelemor, Inc. Computing system with hardware bus management and method of operation thereof
US11494322B2 (en) 2011-05-06 2022-11-08 Xcelemor, Inc. Computing system with hardware reconfiguration mechanism and method of operation thereof
US20120284439A1 (en) * 2011-05-06 2012-11-08 Xcelemor, Inc. Computing system with hardware bus management and method of operation thereof
US10558437B1 (en) * 2013-01-22 2020-02-11 Altera Corporation Method and apparatus for performing profile guided optimization for high-level synthesis
US20160063226A1 (en) * 2014-09-03 2016-03-03 Microsoft Corporation Shared Session Techniques
US9495522B2 (en) * 2014-09-03 2016-11-15 Microsoft Technology Licensing, Llc Shared session techniques
US20160321081A1 (en) * 2015-05-02 2016-11-03 Hyeung-Yun Kim Embedded systems of internet-of-things incorporating a cloud computing service of FPGA reconfiguration
US20210255897A1 (en) * 2017-09-29 2021-08-19 Intel Corporation Technologies for opportunistic acceleration overprovisioning for disaggregated architectures
US10621299B1 (en) * 2018-02-05 2020-04-14 Xilinx, Inc. Dynamic platform support in programmable integrated circuits
US10608641B2 (en) 2018-07-20 2020-03-31 Xilinx, Inc. Hierarchical partial reconfiguration for programmable integrated circuits
US10891414B2 (en) * 2019-05-23 2021-01-12 Xilinx, Inc. Hardware-software design flow for heterogeneous and programmable devices
US11188312B2 (en) 2019-05-23 2021-11-30 Xilinx, Inc. Hardware-software design flow with high-level synthesis for heterogeneous and programmable devices
US11301295B1 (en) 2019-05-23 2022-04-12 Xilinx, Inc. Implementing an application specified as a data flow graph in an array of data processing engines
US11645053B2 (en) 2019-05-23 2023-05-09 Xilinx, Inc. Hardware-software design flow with high-level synthesis for heterogeneous and programmable devices
US10977018B1 (en) 2019-12-05 2021-04-13 Xilinx, Inc. Development environment for heterogeneous devices
US11886789B1 (en) 2021-07-07 2024-01-30 Xilinx, Inc. Block design containers for circuit design

Also Published As

Publication number Publication date
US20190205271A1 (en) 2019-07-04
WO2012154691A1 (fr) 2012-11-15
US20120284438A1 (en) 2012-11-08
US20120284379A1 (en) 2012-11-08
US9152748B2 (en) 2015-10-06
US11494322B2 (en) 2022-11-08
US9053266B2 (en) 2015-06-09
US20120284492A1 (en) 2012-11-08
US20120284439A1 (en) 2012-11-08
WO2012154612A1 (fr) 2012-11-15
US20150234755A1 (en) 2015-08-20
WO2012154586A1 (fr) 2012-11-15
US8756548B2 (en) 2014-06-17
WO2012154616A2 (fr) 2012-11-15
US8868894B2 (en) 2014-10-21
WO2012154616A3 (fr) 2014-05-01
US9495310B2 (en) 2016-11-15
US8869087B2 (en) 2014-10-21
US20120284502A1 (en) 2012-11-08
WO2012154596A1 (fr) 2012-11-15

Similar Documents

Publication Publication Date Title
US11494322B2 (en) Computing system with hardware reconfiguration mechanism and method of operation thereof
US8756601B2 (en) Memory coherency acceleration via virtual machine migration
CN118012572A (zh) 用于自动配置用于容器应用的最小云服务访问权限的技术
US20160202999A1 (en) A Computing Platform, A Reconfigurable Hardware Device And A Method for Simultaneously Executing Processes On Dynamically Reconfigurable Hardware Device, Such As An FPGA, As Well As Instruction Set Processors, Such As A CPU, And A Related Computer Readable Medium
CN106537336B (zh) 云固件
US20110265093A1 (en) Computer System and Program Product
EP2704009A2 (fr) Appareil de traitement d' informations, procédé et programme de traitement d'informations
CN112306625A (zh) 一种部署虚拟机的方法及相关装置
Wei et al. Optimizing gpu sharing for container-based dnn serving with multi-instance gpus
EP4345615A1 (fr) Procédé, appareil et système de gestion de ressources de stockage pour un groupe de conteneurs
JP5420477B2 (ja) 情報サービスシステム
Afonso et al. Heterogeneous CPU/FPGA reconfigurable computing system for avionic test application
US11847611B2 (en) Orchestrating and automating product deployment flow and lifecycle management
CN114371911B (zh) 虚拟机调度方法、装置、电子设备和可读存储介质
CN113396402B (en) Method and apparatus for controlling memory processing
CN121444075A (zh) 控制装置、程序以及系统
CN119806728A (zh) 一种计算节点的容器引擎和容器编排方法
CN121217735A (zh) 一种nfv基础设施功能卸载的方法及相关装置
CN121166331A (zh) 一种系统服务的调用方法及相关装置
CN121092047A (zh) 分布式存储方法、系统和服务器
Viskic Modeling and synthesis of communication software for multi-processor systems-on-chip
WO2018107860A1 (fr) Procédé et dispositif d'exploitation de service, et système informatique en nuage
KR20050040397A (ko) 시스템 버스 구성 방법 및 시스템 버스 제어기

Legal Events

Date Code Title Description
AS Assignment

Owner name: XCELEMOR, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZIEVERS, PETER J.;REEL/FRAME:028160/0601

Effective date: 20120503

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