Patent Grant
11488350
This disclosure relates generally to graphics processor architecture and more particularly to circuitry configured to compress pixel write data generated by compute tasks.
Computing devices may compress various types of data, e.g., to reduce memory footprint or bandwidth. Certain types of tasks such as graphics pixel shaders may write data in convenient blocks for compressing. Other types of tasks, such as compute kernels, may generate more arbitrary writes. Compute kernels may perform image processing for various purposes, e.g., for post-processing in computer gaming or for computational photography.
This specification includes references to various embodiments, to indicate that the present disclosure is not intended to refer to one particular implementation, but rather a range of embodiments that fall within the spirit of the present disclosure, including the appended claims. Particular features, structures, or characteristics may be combined in any suitable manner consistent with this disclosure.
Within this disclosure, different entities (which may variously be referred to as “units,” “circuits,” other components, etc.) may be described or claimed as “configured” to perform one or more tasks or operations. This formulation—[entity] configured to [perform one or more tasks]—is used herein to refer to structure (i.e., something physical, such as an electronic circuit). More specifically, this formulation is used to indicate that this structure is arranged to perform the one or more tasks during operation. A structure can be said to be “configured to” perform some task even if the structure is not currently being operated. A “compression circuit configured to compress a block of pixel data” is intended to cover, for example, a circuit that performs this function during operation, even if the circuit in question is not currently being used (e.g., power is not connected to it). Thus, an entity described or recited as “configured to” perform some task refers to something physical, such as a device, circuit, memory storing program instructions executable to implement the task, etc. This phrase is not used herein to refer to something intangible.
The term “configured to” is not intended to mean “configurable to.” An unprogrammed FPGA, for example, would not be considered to be “configured to” perform some specific function, although it may be “configurable to” perform that function. After appropriate programming, the FPGA may then be configured to perform that function.
Reciting in the appended claims that a structure is “configured to” perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) for that claim element. Accordingly, none of the claims in this application as filed are intended to be interpreted as having means-plus-function elements. Should Applicant wish to invoke Section 112(f) during prosecution, it will recite claim elements using the “means for” [performing a function] construct.
As used herein, the term “based on” is used to describe one or more factors that affect a determination. This term does not foreclose the possibility that additional factors may affect the determination. That is, a determination may be solely based on specified factors or based on the specified factors as well as other, unspecified factors. Consider the phrase “determine A based on B.” This phrase specifies that B is a factor that is used to determine A or that affects the determination of A. This phrase does not foreclose that the determination of A may also be based on some other factor, such as C. This phrase is also intended to cover an embodiment in which A is determined based solely on B. As used herein, the phrase “based on” is synonymous with the phrase “based at least in part on.”
Further, as used herein, the terms “first,” “second,” “third,” etc. do not necessarily imply an ordering (e.g., temporal) between elements. For example, a referring to a “first” graphics operation and a “second” graphics operation does not imply an ordering of the graphics operation, absent additional language constraining the temporal relationship between these operations. In short, references such as “first,” “second,” etc. are used as labels for ease of reference in the description and the appended claims.
Graphics Processing Overview
Referring to
Referring now to
Vertex pipe 185, in the illustrated embodiment, may include various fixed-function hardware configured to process vertex data. Vertex pipe 185 may be configured to communicate with programmable shader 160 in order to coordinate vertex processing. In the illustrated embodiment, vertex pipe 185 is configured to send processed data to fragment pipe 175 and/or programmable shader 160 for further processing.
Fragment pipe 175, in the illustrated embodiment, may include various fixed-function hardware configured to process pixel data. Fragment pipe 175 may be configured to communicate with programmable shader 160 in order to coordinate fragment processing. Fragment pipe 175 may be configured to perform rasterization on polygons from vertex pipe 185 and/or programmable shader 160 to generate fragment data. Vertex pipe 185 and/or fragment pipe 175 may be coupled to memory interface 180 (coupling not shown) in order to access graphics data.
Programmable shader 160, in the illustrated embodiment, is configured to receive vertex data from vertex pipe 185 and fragment data from fragment pipe 175 and/or TPU 165. Programmable shader 160 may be configured to perform vertex processing tasks on vertex data which may include various transformations and/or adjustments of vertex data. Programmable shader 160, in the illustrated embodiment, is also configured to perform fragment processing tasks on pixel data such as texturing and shading, for example. Programmable shader 160 may include multiple execution pipelines for processing data in parallel, e.g., in a single-instruction multiple-data (SIMD) fashion.
TPU 165, in the illustrated embodiment, is configured to schedule fragment processing tasks from programmable shader 160. In some embodiments, TPU 165 is configured to pre-fetch texture data and assign initial colors to fragments for further processing by programmable shader 160 (e.g., via memory interface 180). TPU 165 may be configured to provide fragment components in normalized integer formats or floating-point formats, for example. In some embodiments, TPU 165 is configured to provide fragments in groups of four (a “fragment quad”) in a 2×2 format to be processed by a group of four execution pipelines in programmable shader 160.
Image write unit (IWU) 170, in some embodiments, is configured to store processed tiles of an image and may perform operations to a rendered image before it is transferred for display or to memory for storage. In some embodiments, graphics unit 150 is configured to perform tile-based deferred rendering (TBDR). In tile-based rendering, different portions of the screen space (e.g., squares or rectangles of pixels) may be processed separately before being combined into a frame. Memory interface 180 may facilitate communications with one or more of various memory hierarchies in various embodiments.
Programmable shader 160 may execute compute tasks that write pixel data. This pixel data may be written arbitrarily according to instructions of a compute kernel such that it is unknown when a block of consecutively-addressed pixel writes will be available for compression. In some embodiments, the device is configured to accumulate and compress opportunistically based on data stored in first level cache 210 and also configured to compress based on data stored in second level cache 220. In embodiments where second level cache 220 is larger than first level cache 210, the higher level may be more likely to fully accumulate blocks for compression. Although various examples are discussed herein in the context of compute tasks, similar techniques may be used for various types of graphics work, including pixel shaders with arbitrary pixel writes, for example.
First level cache 210 and second level cache 220 may be implemented using any of various caching technologies, and may or may not share characteristics such as associativity, write-though or write-back implementation, storage circuit technology, tag size, etc. As discussed above, in some embodiments the second level cache 220 is configured to store a greater amount of data than first level cache 210. In some embodiments, second level cache 220 is a shared cache (e.g., among multiple programmable shaders, a texture processing unit, image write buffer, etc.).
Compression circuitry 216 and compression/pack circuitry 226, in some embodiments, are configured to compress blocks of data. In some embodiments, compression circuitry is configured to operate on data blocks of one or more sizes. For example, compression circuitry 216 may be configured to operate on 64, 128, or 256 bytes of data, in various embodiments. Depending on the precision used for pixel data, this may correspond to pixel write data for sets of 4×4, 8×4, or 8×8, pixels, for example.
Circuitry 216 and 226 may use the same compression algorithm or different compression algorithms. In some embodiments, compression circuitry may use multiple predictors in parallel and pick the best predictor to encode a given block. In some embodiments, compression circuitry 216 is configured to compress any blocks that are fully accumulated in first level cache 210 before writing compressed blocks to second level cache 220. A data block or data structure is “fully accumulated” in a storage element when all data elements of that block or structure are stored in that storage element. For example, for an 8×4 block of pixel data, the block is fully accumulated when pixel data for all thirty-two pixels is stored, but not fully accumulated if data for one or more pixels is not stored. Compression may still be performed on a data block that is not fully accumulated (e.g., by filling in default values for missing data in a block), but in some embodiments such filling is delayed until compression/pack circuitry 226 in order to determine if any older writes should be combined with the data block.
If compression circuitry 216 does not fully accumulate a block before it needs to be evicted from first level cache 210, it may store the evicted portion of the block in second level cache 220 without compression. Therefore, in some embodiments, compression circuitry 216 may send metadata to second level cache 220 indicating the status (e.g., compressed or not) of blocks of data. Metadata may also indicate whether data blocks are fully accumulated at one or more cache levels.
Compression/pack circuitry 226, in some embodiments, is configured to pack compressed blocks into a macro-block for a combined write to a higher level in the storage hierarchy. In some embodiments, a macro-block includes multiple blocks, e.g., 8 or 32 blocks. In some embodiments, the macro-block size is smaller than or equal to the number of pixels processed by a graphics workgroup (e.g., the size of a thread group times the number of pixels per thread). In some embodiments, the size of a macro-block corresponds to the size of a cache line in the second level cache 220.
If some blocks of a macro-block are not compressed but can be fully accumulated in second level cache 220, circuitry 226 may compress those blocks. If a macro-block needs to be written to memory but some of its blocks are not fully accumulated, circuitry 216 may read older data from memory for incomplete blocks and attempt to fully accumulate the blocks for compression. A more detailed discussion of such techniques is included below with reference to
Note that PBE circuitry 305, 310, and 318 may be included in an example implementation of the image write buffer unit 170 of
PBE datapath 305, in the illustrated embodiment, is configured to receive pixel writes from programmable shader 160 and may perform one or more operations on received pixel data. In the illustrated embodiment, PBE datapath 305 is configured to send data for macro-block (MB) compressible writes to MUX 329 and bypass the PBE cache. These types of writes may have full accumulation for each block in a macro-block. Programmable shader 160 may include information with writes indicating whether they are macro-block compressible. Compressor 316 may compress each block within a MB compressible write and store the data in L2 cache 320 (or alternatively may compress the macro-block as a whole, in some embodiments). In the illustrated embodiment, PBE datapath 305 is configured to store data for non-MB-compressible writes in PBE cache 310. PBE cache control 318, in some embodiments, is configured to control various functionality of PBE cache 310, including allocation, eviction, maintaining cache metadata such as least-recently-used information, etc.
Compressor 316, in the illustrated embodiment, is configured to receive data from PBE cache 310 (e.g., evicted data) and compress fully accumulated blocks of the pixel data. Compressor 316, in the illustrated embodiment, is configured to store blocks (whether compressed or not) in L2 cache 320, along with metadata indicating the status of stored blocks. Note that metadata may be stored together in one or more cache lines of L2 cache 320 to reduce interference with the operation of L2 cache 320. In some embodiments, a separate hardware metadata buffer may be implemented in order to accumulate metadata for combined writes. For blocks that are not fully accumulated, compressor 316 may not compress those blocks but may store them in uncompressed form in L2 cache 320.
Macro-block scoreboard 312, in some embodiments, is configured to track the fullness and locations of macro-blocks within L2 cache 320. The scoreboard entries may track validity, macro-block base address, compression format, macro-block size, packed format, metadata address for the macro-block, number of pixels needed for a macro-block to be complete, sub-block state information, timeout status, etc. Macro-block scoreboard 312 may evict macro-blocks in response to detecting full accumulation. In some embodiments, macro-block scoreboard 312 is configured to evict partially-covered macro-blocks after a time-out interval (which may reduce eviction of macro-blocks needed for a cache flush invalidate, for example, because timed-out macro-blocks will have already been evicted). In some embodiments, to evict a macro-block, macro-block scoreboard 312 is configured to send an evict command for each cache line in the macro-block to L2 cache 320, which sends the evicted lines to macro-block staging buffer 314 and marks the evicted line as clean and invalid.
Macro-block staging buffer 314, in some embodiments, is configured to receive blocks from L2 cache 320 and send blocks to compress/pack circuitry 326. In some embodiments, buffer 314 sends one block of a macro-block at a time, in order.
Compress/pack circuitry 326 may compress uncompressed blocks, pack compressed blocks, and send the blocks to memory management unit 340 for a combined write to memory. Note that packing may include adjusting the addresses of compressed blocks after compression, given their reduced size, for a combined write of blocks in the macro-block. In some embodiments, compress circuitry 326 and compressor 316 implement different compression algorithms.
For blocks that are not fully accumulated, macro-block staging buffer 314 may check for older write data in memory via memory management unit 340. Decompressor 330 may decompress reads of older data from memory (if compressed) and macro-block staging buffer 314 may attempt to combine the old write data from memory with the new block. If the combination provides full accumulation, compress circuitry 326 may compress the block normally. If the combination does not provide full accumulation, the device may fill remaining portions of the block prior to compression.
As shown, L2 cache 320 may bypass the staging buffer 314 and compress/pack circuitry 326 via MUX 328, e.g., for macro-block compressible writes or for non-compressed writes. In some embodiments, the device is configured to turn off compute compression during one or more processing intervals, e.g., such that pixel writes from compute kernels are not compressed and circuitry 316 and 326 is disabled.
Block A, in the illustrated example, is complete in the PBE cache. Therefore, upon eviction, compressor 316 compresses block A before it is stored in the L2 cache. Block B, in the illustrated example, is incomplete in the PBE cache and therefore is not compressed when stored in the L2 cache. In the illustrated example, block B remains incomplete in the L2 cache, and may be handled according to
At 510, in the illustrated embodiment, macro-block staging buffer 314 receives an incomplete block that has been evicted from L2 cache 320. At 520, the device determines whether the incomplete block has already been written in memory. If not, flow proceeds to 530 and the device fills missing pixels (e.g., with default value(s), with value(s) based on other pixels that are accumulated in the block such as color values from the first accumulated pixel in the block, etc.).
If the block has previously been written to memory, flow proceeds to 540 and the device determines if the block was compressed in memory. This determination may be based on metadata previously generated for the block, which may be cached or stored in the memory and associated with the block. If not compressed, the device reads the block at 560, combines the data from memory with the data in the macro-block staging buffer 314, fills any missing pixels, and compresses the block. If compressed, the device reads the block at 550, decompresses the block using decompressor 330, combines the data from memory with the data in the macro-block staging buffer 314, fills any missing pixels, and compresses the block.
At 610, in the illustrated embodiment, programmable shader circuitry executes program instructions of a compute kernel that writes pixel data.
At 620, in the illustrated embodiment, first cache circuitry stores pixel write data from the computer kernel.
At 630, in the illustrated embodiment, first compression circuitry compresses a first block of pixel write data in response to full accumulation of the first block in the first cache circuitry. In some embodiments, for a type of write by the programmable shader circuitry that includes complete data for a threshold number of blocks (e.g., a macro-block compressible write) the device is configured to send multiple blocks of pixel write data to the pixel write circuitry without storing them in the first cache circuitry.
At 640, in the illustrated embodiment, second cache circuitry stores pixel write data from the computer kernel, where the second cache circuitry is at a higher level in a storage hierarchy than the first cache circuitry. In some embodiments, the device stores metadata in the second cache circuitry for the first and second blocks, where the metadata indicates whether the first and second blocks have been compressed by the first compression circuitry.
At 650, in the illustrated embodiment, second compression circuitry compresses a second block of pixel write data in response to full accumulation of the second block in the second cache circuitry. Note that the second block may not have been fully accumulated in the first cache circuitry, for example, but may be fully accumulated in the second cache circuitry due to its larger size.
In some embodiments, the devices includes tracking circuitry (e.g., macro-block scoreboard 312) that tracks respective accumulation status of a number of blocks of pixel write data. In some embodiments, in response to an eviction from the second caching circuitry of a third block of pixel write data that is not fully accumulated, the device in response to determining that corresponding data for the third block is not stored at a higher level in the storage hierarchy, inserts fill data for missing pixels and compresses the filled third block. Further, in response to determining that corresponding data for the third block is stored at a higher level in the storage hierarchy, the device may read the corresponding data, combine the read data with pixel write data for the third block, and compress the combined third block. Further, if the read data is compressed, decompressor circuitry may decompress the read data in response to determining that corresponding data for the third block is stored at a higher level in the storage hierarchy in a compressed format.
At 660, in the illustrated embodiment, write circuitry writes the first and second compressed blocks of pixel data in a combined write to a higher level in the storage hierarchy. The combined write may store pixel data for a graphics workgroup operating on a tile of a graphics frame and the first and second blocks may include pixel data for different portions of the tile.
In various embodiments, the disclosed techniques may advantageously reduce memory bandwidth by compressing data before writes to memory and may also reduce the footprint of pixel data in memory. This may improve performance or reduce power consumption relative to traditional techniques. Further, the disclosed multi-level compression techniques may improve compression performance, improve compression ratios, etc. while maintaining proper pixel data for pixels written at different times.
Referring now to
Fabric 710 may include various interconnects, buses, MUX's, controllers, etc., and may be configured to facilitate communication between various elements of device 700. In some embodiments, portions of fabric 710 may be configured to implement various different communication protocols. In other embodiments, fabric 710 may implement a single communication protocol and elements coupled to fabric 710 may convert from the single communication protocol to other communication protocols internally.
In the illustrated embodiment, compute complex 720 includes bus interface unit (BIU) 725, cache 730, and cores 735 and 740. In various embodiments, compute complex 720 may include various numbers of processors, processor cores and/or caches. For example, compute complex 720 may include 1, 2, or 4 processor cores, or any other suitable number. In one embodiment, cache 730 is a set associative L2 cache. In some embodiments, cores 735 and/or 740 may include internal instruction and/or data caches. In some embodiments, a coherency unit (not shown) in fabric 710, cache 730, or elsewhere in device 700 may be configured to maintain coherency between various caches of device 700. BIU 725 may be configured to manage communication between compute complex 720 and other elements of device 700. Processor cores such as cores 735 and 740 may be configured to execute instructions of a particular instruction set architecture (ISA) which may include operating system instructions and user application instructions.
Cache/memory controller 745 may be configured to manage transfer of data between fabric 710 and one or more caches and/or memories. For example, cache/memory controller 745 may be coupled to an L3 cache, which may in turn be coupled to a system memory. In other embodiments, cache/memory controller 745 may be directly coupled to a memory. In some embodiments, cache/memory controller 745 may include one or more internal caches.
As used herein, the term “coupled to” may indicate one or more connections between elements, and a coupling may include intervening elements. For example, in
Graphics unit 150 may include one or more processors and/or one or more graphics processing units (GPU's). Graphics unit 150 may receive graphics-oriented instructions, such as OPENGL®, Metal, or DIRECT3D® instructions, for example. Graphics unit 150 may execute specialized GPU instructions or perform other operations based on the received graphics-oriented instructions. Graphics unit 150 may generally be configured to process large blocks of data in parallel and may build images in a frame buffer for output to a display. Graphics unit 150 may include transform, lighting, triangle, and/or rendering engines in one or more graphics processing pipelines. Graphics unit 150 may output pixel information for display images. Programmable shader 160, in various embodiments, may include highly parallel execution cores configured to execute graphics programs, which may include pixel tasks, vertex tasks, and compute tasks (which may or may not be graphics-related).
In some embodiments, programmable shader 160 includes disclosed caching and compression circuitry.
Display unit 765 may be configured to read data from a frame buffer and provide a stream of pixel values for display. Display unit 765 may be configured as a display pipeline in some embodiments. Additionally, display unit 765 may be configured to blend multiple frames to produce an output frame. Further, display unit 765 may include one or more interfaces (e.g., MIPI® or embedded display port (eDP)) for coupling to a user display (e.g., a touchscreen or an external display).
I/O bridge 750 may include various elements configured to implement: universal serial bus (USB) communications, security, audio, and/or low-power always-on functionality, for example. I/O bridge 750 may also include interfaces such as pulse-width modulation (PWM), general-purpose input/output (GPIO), serial peripheral interface (SPI), and/or inter-integrated circuit (I2C), for example. Various types of peripherals and devices may be coupled to device 700 via I/O bridge 750.
The present disclosure has described various example circuits in detail above. It is intended that the present disclosure cover not only embodiments that include such circuitry, but also a computer-readable storage medium that includes design information that specifies such circuitry. Accordingly, the present disclosure is intended to support claims that cover not only an apparatus that includes the disclosed circuitry, but also a storage medium that specifies the circuitry in a format that is recognized by a fabrication system configured to produce hardware (e.g., an integrated circuit) that includes the disclosed circuitry. Claims to such a storage medium are intended to cover, for example, an entity that produces a circuit design, but does not itself fabricate the design.
Non-transitory computer-readable storage medium 810, may comprise any of various appropriate types of memory devices or storage devices. Non-transitory computer-readable storage medium 810 may be an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. Non-transitory computer-readable storage medium 810 may include other types of non-transitory memory as well or combinations thereof. Non-transitory computer-readable storage medium 810 may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network.
Design information 815 may be specified using any of various appropriate computer languages, including hardware description languages such as, without limitation: VHDL, Verilog, SystemC, SystemVerilog, RHDL, M, MyHDL, etc. Design information 815 may be usable by semiconductor fabrication system 820 to fabricate at least a portion of integrated circuit 830. The format of design information 815 may be recognized by at least one semiconductor fabrication system 820. In some embodiments, design information 815 may also include one or more cell libraries which specify the synthesis and/or layout of integrated circuit 830. In some embodiments, the design information is specified in whole or in part in the form of a netlist that specifies cell library elements and their connectivity. Design information 815, taken alone, may or may not include sufficient information for fabrication of a corresponding integrated circuit. For example, design information 815 may specify the circuit elements to be fabricated but not their physical layout. In this case, design information 815 may need to be combined with layout information to actually fabricate the specified circuitry.
Integrated circuit 830 may, in various embodiments, include one or more custom macrocells, such as memories, analog or mixed-signal circuits, and the like. In such cases, design information 815 may include information related to included macrocells. Such information may include, without limitation, schematics capture database, mask design data, behavioral models, and device or transistor level netlists. As used herein, mask design data may be formatted according to graphic data system (GDSII), or any other suitable format.
Semiconductor fabrication system 820 may include any of various appropriate elements configured to fabricate integrated circuits. This may include, for example, elements for depositing semiconductor materials (e.g., on a wafer, which may include masking), removing materials, altering the shape of deposited materials, modifying materials (e.g., by doping materials or modifying dielectric constants using ultraviolet processing), etc. Semiconductor fabrication system 820 may also be configured to perform various testing of fabricated circuits for correct operation.
In various embodiments, integrated circuit 830 is configured to operate according to a circuit design specified by design information 815, which may include performing any of the functionality described herein. For example, integrated circuit 830 may include any of various elements shown in
As used herein, a phrase of the form “design information that specifies a design of a circuit configured to . . . ” does not imply that the circuit in question must be fabricated in order for the element to be met. Rather, this phrase indicates that the design information describes a circuit that, upon being fabricated, will be configured to perform the indicated actions or will include the specified components.
Although specific embodiments have been described above, these embodiments are not intended to limit the scope of the present disclosure, even where only a single embodiment is described with respect to a particular feature. Examples of features provided in the disclosure are intended to be illustrative rather than restrictive unless stated otherwise. The above description is intended to cover such alternatives, modifications, and equivalents as would be apparent to a person skilled in the art having the benefit of this disclosure.
The scope of the present disclosure includes any feature or combination of features disclosed herein (either explicitly or implicitly), or any generalization thereof, whether or not it mitigates any or all of the problems addressed herein. Accordingly, new claims may be formulated during prosecution of this application (or an application claiming priority thereto) to any such combination of features. In particular, with reference to the appended claims, features from dependent claims may be combined with those of the independent claims and features from respective independent claims may be combined in any appropriate manner and not merely in the specific combinations enumerated in the appended claims.
The present application is a continuation of U.S. application Ser. No. 16/673,883, filed Nov. 4, 2019, which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6919904 | Kilgariff | Jul 2005 | B1 |
| 8928681 | Edmondson et al. | Jan 2015 | B1 |
| 9734548 | Hakura et al. | Aug 2017 | B2 |
| 20050071579 | Luick | Mar 2005 | A1 |
| 20070146380 | Nystad | Jun 2007 | A1 |
| 20150331619 | Zheng | Nov 2015 | A1 |
| 20170278215 | Appu et al. | Sep 2017 | A1 |
| 20180075574 | Brennan et al. | Mar 2018 | A1 |
| 20180075584 | Akenine-Moller | Mar 2018 | A1 |
| 20190206090 | Ray | Jul 2019 | A1 |
| 20190354482 | Lee | Nov 2019 | A1 |
| 20200210343 | Tomei | Jul 2020 | A1 |
| 20200372603 | Rangan | Nov 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2018057109 | Mar 2018 | WO |
| Entry |
|---|
| International Preliminary Report on Patentability in PCT Appl. No. PCT/US2020/053679 dated May 19, 2022, 9 pages. |
| Jelena Trajkovic et al, “Improving SDRAM access energy efficiency for low-power embedded systems,” ACM Transactions On Embedded Computing Systems, ACM, New York, NY, US, vol. 7, No. 3, May 8, 2008 (May 8, 2008), pp. 1-21, XP058099898, ISSN: 1539-9087, DOI: 10.1145/1347375.1347377. |
| Number | Date | Country | |
|---|---|---|---|
| 20210295593 A1 | Sep 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16673883 | Nov 2019 | US |
| Child | 17338846 | US |
