IP Library › Granted Patent US 12,596,650
Granted Patent B2
US 12,596,650 · App. 18/375,018 · Granted Apr 7, 2026

Preemptive flushing of processing-in-memory data structures

Inventors: David Andrew Werner (Austin, TX); Travis Henry Boraten (Austin, TX); Michael Warren Boyer (Redmond, WA)
Assignee: Advanced Micro Devices, Inc.
G06F12/0897G06F12/0891G06F2212/1021
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,596,650
App. No.
18/375,018
Granted
Apr 7, 2026
Kind
B2
Abstract

Preemptive flushing of data involved in executing a processing-in-memory command, from a cache system to main memory that is accessible by a processing-in-memory component, is described. In one example, a system includes an asynchronous flush controller that receives an indication of a subsequent processing-in-memory command to be executed as part of performing a computational task. While earlier commands of the computational task are executed, the asynchronous flush controller evicts or invalidates data elements involved in executing the subsequent processing-in-memory command from the cache system, such that the processing-in-memory command can proceed without stalling.

Claims (33)

1 . A system comprising:

a cache system including a plurality of cache levels; and

a cache controller configured to:

identify that a processing-in-memory command involves a plurality of data elements stored at an address range in the cache system; and

responsive to the address range satisfying a threshold size, evict a portion of the plurality of data elements from the cache system prior to issuance of the processing-in-memory command, the evicted portion of the plurality of data elements excluding some of the plurality of data elements.

2 . The system of claim 1 , wherein the processing-in-memory command is associated with a computational task, and wherein the cache controller is configured to identify that the processing-in-memory command involves the plurality of data elements stored at the address range in the cache system based on code for the computational task including a non-processing-in-memory command that modifies at least one of the plurality of data elements prior to issuance of the processing-in-memory command.

3 . The system of claim 1 , wherein the cache controller is configured to evict the portion of the plurality of data elements from the cache system by transmitting a clean command to the cache system that specifies a portion of the address range including the portion of the plurality of data elements and an instruction to flush the portion of the plurality of data elements to memory of the system or invalidate the portion of the plurality of data elements in the cache system.

4 . The system of claim 3 , wherein the processing-in-memory command is associated with a computational task, and wherein the cache controller generates the clean command by performing a cache directory lookup for the portion of the plurality of data elements during execution of one or more different commands involved in performing the computational task.

5 . The system of claim 4 , wherein the cache controller generates the portion of the address range of the clean command based on one or more cache hit responses to the cache directory lookup.

6 . The system of claim 4 , wherein the cache controller performs the cache directory lookup by skipping a beginning portion of the plurality of data elements based on the address range in the cache system satisfying the threshold size.

7 . The system of claim 6 , wherein the threshold size for the address range in the cache system is based on a storage size of the cache system.

8 . The system of claim 4 , wherein the cache controller performs the cache directory lookup by skipping a threshold number of the plurality of data elements based on the cache directory lookup returning a number of successive cache misses.

9 . The system of claim 3 , wherein the processing-in-memory command is associated with a computational task, and wherein the cache controller transmits the clean command during execution of one or more different commands involved in performing the computational task.

10 . A device comprising:

a cache controller configured to:

receive an indication that a processing-in-memory command to be subsequently executed involves a plurality of data elements;

perform a cache directory lookup to determine whether the plurality of data elements are stored at an address range in a cache system; and

responsive to the address range satisfying a threshold size, evict a portion of the plurality of data elements from the cache system prior to issuance of the processing-in-memory command, the evicted portion of the plurality of data elements excluding some of the plurality of data elements.

11 . The device of claim 10 , wherein the cache controller evicts the portion of the plurality of data elements from the cache system by transmitting a clean command to the cache system that specifies a portion of the address range including the plurality of data elements and an instruction to flush the portion of the plurality of data elements to memory or invalidate the portion of the plurality of data elements in the cache system.

12 . The device of claim 11 , wherein the cache controller performs the cache directory lookup by skipping a beginning portion of the plurality of data elements included in the address range in response to the address range satisfying the threshold size.

13 . The device of claim 12 , wherein the threshold size for the address range is based on a storage size of the cache system.

14 . The device of claim 11 , wherein the processing-in-memory command is associated with a computational task, and wherein the cache controller generates the clean command by performing a cache directory lookup for the portion of the plurality of data elements included in the address range during execution of one or more different commands involved in performing the computational task.

15 . The device of claim 14 , wherein the cache controller generates the portion of the address range specified by the clean command based on one or more cache hit responses to the cache directory lookup.

16 . The device of claim 11 , wherein the cache controller performs the cache directory lookup by skipping a threshold number of the plurality of data elements based on the cache directory lookup returning a number of successive cache misses.

17 . The device of claim 11 , wherein the processing-in-memory command is associated with a computational task, and wherein the cache controller transmits the clean command during execution of one or more different commands involved in performing the computational task.

18 . The device of claim 11 , wherein the processing-in-memory command is associated with a computational task, and wherein the indication that the processing-in-memory command involves the plurality of data elements stored in the cache system is generated based on code for the computational task including a non-processing-in-memory command that modifies at least one of the plurality of data elements prior to issuance of the processing-in-memory command.

19 . A method comprising:

executing, by a core of a processing unit, a plurality of commands as part of performing a computational task;

identifying that the plurality of commands include a processing-in-memory instruction that accesses a plurality of data elements stored at an address range in a cache system during performance of the computational task;

identifying that the address range satisfies a threshold size;

responsive to the address range satisfying the threshold size, and while the core of the processing unit is executing a portion of the plurality of commands that occur prior to the processing-in-memory instruction, evicting a portion of the plurality of data elements from the cache system, the portion of the plurality of data elements excluding at least one of the plurality of data elements; and

transmitting, by the core of the processing unit, the processing-in-memory instruction to a processing-in-memory component after the portion of the plurality of data elements is evicted from the cache system.

20 . The method of claim 19 , wherein evicting the portion of the plurality of data elements is performed without evicting all of the plurality of data elements from the cache system.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2023
From: WERNER, DAVID ANDREW; BORATEN, TRAVIS HENRY; BOYER, MICHAEL WARREN
To: ADVANCED MICRO DEVICES, INC
Reel/Frame 065075/0889 →
Continuity (1)
Related Publication 20250110887A1 · Apr 3, 2025
References Cited (158)
US 6263406B1 · Uwano · 2001 [cited by applicant]
US 6553465B1 · Takusagawa · 2003 [cited by applicant]
US 6560693B1 · Puzak et al. · 2003 [cited by applicant]
US 6944746B2 · So · 2005 [cited by applicant]
US 7047393B2 · Paver · 2006 [cited by applicant]
US 8359462B1 · Khan et al. · 2013 [cited by applicant]
US 9575815B1 · Guthrie et al. · 2017 [cited by applicant]
US 10061588B2 · Gschwind et al. · 2018 [cited by applicant]
US 11119923B2 · Farmahini Farahani et al. · 2021 [cited by applicant]
US 11487447B2 · Islam et al. · 2022 [cited by applicant]
US 11594274B2 · Murphy et al. · 2023 [cited by applicant]
US 11625249B2 · Kotra et al. · 2023 [cited by applicant]
US 11625251B1 · Agrawal et al. · 2023 [cited by applicant]
US 11663008B2 · Lee et al. · 2023 [cited by applicant]
US 11782624B2 · Yang et al. · 2023 [cited by applicant]
US 11797201B2 · Islam et al. · 2023 [cited by applicant]
US 11868777B2 · Kalamatianos et al. · 2024 [cited by applicant]
US 12032829B2 · Kim et al. · 2024 [cited by applicant]
US 12073251B2 · Challapalle et al. · 2024 [cited by applicant]
US 12153926B2 · Kalamatianos et al. · 2024 [cited by applicant]
US 12160643B2 · Zhou et al. · 2024 [cited by applicant]
US 12265470B1 · Boraten et al. · 2025 [cited by applicant]
US 12380029B2 · Boraten et al. · 2025 [cited by applicant]
US 12455826B2 · Werner et al. · 2025 [cited by applicant]
US 20020199066A1 · Chaudhry et al. · 2002 [cited by applicant]
US 20060101209A1 · Lais et al. · 2006 [cited by applicant]
US 20060224835A1 · Blumrich et al. · 2006 [cited by applicant]
US 20070174685A1 · Banks · 2007 [cited by applicant]
US 20080046692A1 · Michalak et al. · 2008 [cited by applicant]
US 20080244185A1 · O'Krafka et al. · 2008 [cited by applicant]
US 20080307169A1 · Averill et al. · 2008 [cited by applicant]
US 20090313435A1 · Thantry et al. · 2009 [cited by applicant]
US 20100017649A1 · Wu et al. · 2010 [cited by applicant]
US 20100153761A1 · Nishioka · 2010 [cited by applicant]
US 20110242113A1 · Keall et al. · 2011 [cited by applicant]
US 20110276762A1 · Daly et al. · 2011 [cited by applicant]
US 20120069664A1 · Kim et al. · 2012 [cited by applicant]
US 20120159080A1 · Donley et al. · 2012 [cited by applicant]
US 20120179876A1 · Guthrie et al. · 2012 [cited by applicant]
US 20120246395A1 · Cho et al. · 2012 [cited by applicant]
US 20130086367A1 · Gschwind et al. · 2013 [cited by applicant]
US 20140040551A1 · Blainey et al. · 2014 [cited by applicant]
US 20140052916A1 · Lih et al. · 2014 [cited by applicant]
US 20140089572A1 · Koka et al. · 2014 [cited by applicant]
US 20140281405A1 · Streett et al. · 2014 [cited by applicant]
US 20160092238A1 · Codrescu et al. · 2016 [cited by applicant]
US 20160098279A1 · Glew · 2016 [cited by applicant]
US 20160155491A1 · Roberts et al. · 2016 [cited by applicant]
US 20170060588A1 · Choi · 2017 [cited by applicant]
US 20170123915A1 · Nguyen et al. · 2017 [cited by applicant]
US 20170123987A1 · Cheng et al. · 2017 [cited by applicant]
US 20170213312A1 · Woo et al. · 2017 [cited by applicant]
US 20170262369A1 · Murphy · 2017 [cited by applicant]
US 20170337136A1 · Basu et al. · 2017 [cited by applicant]
US 20170344479A1 · Boyer et al. · 2017 [cited by applicant]
US 20170344480A1 · Beard et al. · 2017 [cited by applicant]
US 20180074958A1 · Jayasena et al. · 2018 [cited by applicant]
US 20180089081A1 · Ramalingam · 2018 [cited by applicant]
US 20180188961A1 · Venkatesh et al. · 2018 [cited by applicant]
US 20180336035A1 · Choi et al. · 2018 [cited by applicant]
US 20190018786A1 · Beard et al. · 2019 [cited by applicant]
US 20190089081A1 · Zhang · 2019 [cited by applicant]
US 20200192757A1 · Qin et al. · 2020 [cited by applicant]
US 20200218540A1 · Kesiraju et al. · 2020 [cited by applicant]
US 20210271599A1 · Sharovar · 2021 [cited by applicant]
US 20210271680A1 · Lee et al. · 2021 [cited by applicant]
US 20220075713A1 · Yoon et al. · 2022 [cited by applicant]
US 20220076717A1 · Mathew et al. · 2022 [cited by applicant]
US 20220188117A1 · Kalamatianos et al. · 2022 [cited by applicant]
US 20220188233A1 · Kalamatianos · 2022 [cited by examiner]
US 20220197814A1 · Yudanov · 2022 [cited by applicant]
US 20220206817A1 · Kotra et al. · 2022 [cited by applicant]
US 20220206855A1 · Challapalle et al. · 2022 [cited by applicant]
US 20220206950A1 · Ghodrat et al. · 2022 [cited by applicant]
US 20220276795A1 · Islam et al. · 2022 [cited by applicant]
US 20230066662A1 · Park · 2023 [cited by applicant]
US 20230137467A1 · Moyer · 2023 [cited by applicant]
US 20230244442A1 · Lee et al. · 2023 [cited by applicant]
US 20230244492A1 · Kotra et al. · 2023 [cited by applicant]
US 20230418474A1 · Kim et al. · 2023 [cited by applicant]
US 20240126552A1 · Kalamatianos et al. · 2024 [cited by applicant]
US 20240231645A1 · Zhang et al. · 2024 [cited by applicant]
US 20240330186A1 · Boraten et al. · 2024 [cited by applicant]
US 20250110878A1 · Boraten et al. · 2025 [cited by applicant]
US 20250110886A1 · Boraten et al. · 2025 [cited by applicant]
US 20250181392A1 · Choi et al. · 2025 [cited by applicant]
US 20250307147A1 · Werner et al. · 2025 [cited by applicant]
WO WO2022046371 · 2022 [cited by applicant]
“x86 Instruction Set Reference: CLFLUSH”, Retrieved Jan. 24, 2024. Retrieved from the Internet <https://c9x.me/x86/html/file_module_x86_id_30.html>, 2 pages. [cited by applicant]
U.S. Appl. No. 17/136,767 , “Notice of Allowance”, U.S. Appl. No. 17/136,767, filed Apr. 30, 2024, 18 pages. [cited by applicant]
U.S. Appl. No. 17/473,242 , “Non-Final Office Action”, U.S. Appl. No. 17/473,242, filed Mar. 7, 2024, 16 pages. [cited by applicant]
Nai, Lifeng , et al., “GraphPIM: Enabling Instruction-Level PIM Offloading in Graph Computing Frameworks”, 2017 IEEE International Symposium on High Performance Computer Architecture (HPCA), Feb. 2017, 12 pages. [cited by applicant]
Xu, Sheng , et al., “TUPIM: A Transparent and Universal Processing-in-Memory Architecture for Unmodified Binaries”, GLSVLSI '20: Proceedings of the 2020 on Great Lakes Symposium on VLSI, Sep. 2020, 6 pages. [cited by applicant]
Werner, David Andrew, et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 18/621,319, filed Mar. 29, 2024, 61 pages. [cited by applicant]
U.S. Appl. No. 18/298,723 , “Non-Final Office Action”, U.S. Appl. No. 18/298,723, filed Jun. 20, 2024, 9 pages. [cited by applicant]
“ARM946E-S Technical Reference Manual r1p1”, Arm Developer [retrieved May 17, 2023]. Retrieved from the Internet <https://developer.arm.com/documentation/ddi0201/d/programmer-s-model/cp15-register-map-summary/register-7… [cited by applicant]
“Google Project Zero”, GitHub Inc., Uplaoded by Projects by Google Project Zero [retrieved Sep. 15, 2022]. Retrieved from the Internet <https://github.com/googleprojectzero>., 3 Pages. [cited by applicant]
“HPCA 2021”, The 27th IEEE International Symposium on High-Performance Computer Architecture (HPCA-27), Seoul, South Korea [retrieved Sep. 15, 2022]. Retrieved from the Internet <https://hpca-conf.org/2021/keynotes/>., … [cited by applicant]
U.S. Appl. No. 17/123,270, , “Final Office Action”, U.S. Appl. No. 17/123,270, filed Nov. 23, 2021, 15 pages. [cited by applicant]
U.S. Appl. No. 17/123,270, , “Non-Final Office Action”, U.S. Appl. No. 17/123,270, filed Aug. 4, 2021, 14 pages. [cited by applicant]
U.S. Appl. No. 17/123,270, , “Notice of Allowance”, U.S. Appl. No. 17/123,270, filed Sep. 7, 2023, 7 pages. [cited by applicant]
U.S. Appl. No. 17/123,270, , “Notice of Allowance”, U.S. Appl. No. 17/123,270, filed Nov. 10, 2022, 7 pages. [cited by applicant]
U.S. Appl. No. 17/137,140, , “Final Office Action”, U.S. Appl. No. 17/137,140, filed Aug. 15, 2022, 8 pages. [cited by applicant]
U.S. Appl. No. 17/137, 140, , “Non-Final Office Action”, U.S. Appl. No. 17/137,140, filed Mar. 9, 2022, 8 pages. [cited by applicant]
U.S. Appl. No. 17/137,140, , “Notice of Allowance”, U.S. Appl. No. 17/137,140, filed Dec. 8, 2022, 8 pages. [cited by applicant]
U.S. Appl. No. 17/745,278, , “Non-Final Office Action”, U.S. Appl. No. 17/745,278, filed Feb. 23, 2023, 8 pages. [cited by applicant]
U.S. Appl. No. 17/745,278, , “Notice of Allowance”, U.S. Appl. No. 17/745,278, filed Jun. 14, 2023, 5 pages. [cited by applicant]
Adhinarayanan, Vignesh et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 17/855,157, filed Jun. 30, 2022, 37 pages. [cited by applicant]
Agrawal, Varun et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 17/561,112, filed Dec. 23, 2021, 25 pages. [cited by applicant]
Alsop, Jonathan et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 17/853,613, filed Jun. 29, 2022, 28 pages. [cited by applicant]
Aweke, Zelalem B. et al., “ANVIL: Software-Based Protection Against Next-Generation Rowhammer Attacks”, ACM SIGPLAN Notices, vol. 51, No. 4 [retrieved Sep. 15, 2022]. Retrieved from the Internet <http://www.seclab.cs.st… [cited by applicant]
Boraten, Travis H. et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 18/192,925, filed Mar. 30, 2023, 48 pages. [cited by applicant]
Boraten, Travis H. et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 18/374,951, filed Sep. 29, 2023, 50 pages. [cited by applicant]
Boraten, Travis H. et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 18/374,969, filed Sep. 29, 2023, 51 pages. [cited by applicant]
Boraten, Travis H. , “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 18/146,904, filed Dec. 27, 2022, 53 pages. [cited by applicant]
Boyer, Michael W. et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 17/719,225, filed Apr. 12, 2022, 32 pages. [cited by applicant]
Brasser, Ferdinand et al., “CAn't touch this: software-only mitigation against rowhammer attacks targeting kernel memory”, Proceedings of the 26th USENIX Conference on Security Symposium [retrieved Sep. 15, 2022]. Retri… [cited by applicant]
Cantin, J.F. et al., “Coarse-Grain Coherence Tracking: RegionScout and Region Coherence Arrays”, IEEE Micro, vol. 26, No. 1 [retrieved Oct. 16, 2022]. Retrieved from the Internet <https://pharm.ece.wisc.edu/papers/ieeem… [cited by applicant]
Gulur, Nagendra Dwarakanath et al., “Multiple sub-row buffers in DRAM: unlocking performance and energy improvement opportunities”, Proceedings of the 26th ACM international conference on Supercomputing [retrieved Sep. … [cited by applicant]
Hassan, Hasan et al., “Uncovering In-DRAM RowHammer Protection Mechanisms:A New Methodology, Custom RowHammer Patterns, and Implications”, 54th Annual IEEE/ACM International Symposium on Microarchitecture [retrieved Sep… [cited by applicant]
Jin, Xingyu et al., “Project Zero”, News and updates from the Project Zero team at Google [retrieved Sep. 15, 2022]. Retrieved from the Internet <https://googleprojectzero.blogspot.com/>., Aug. 10, 2022, 15 Pages. [cited by applicant]
Kim, Jeremie S. et al., “Revisiting RowHammer: An Experimental Analysis of Modern DRAM Devices and Mitigation Techniques”, Cornell University arXiv, arXiv.org [retrieved Sep. 15, 2022]. Retrieved from the Internet <http… [cited by applicant]
Kim, Nam Sung , “A Journey to a Commercial-Grade Function-In-Memory (FIM) Chip Development”, HPCA-2021, Keynote [retrieved May 10, 2023]. Retrieved from the Internet <https://hpca-conf.org/2021/keynotes/>., Mar. 3, 2021… [cited by applicant]
Kim, Nam Sung , “A Journey to a Commercial-Grade Processing-In-Memory (PIM) Chip Development”, The 27th IEEE International Symposium on High-Performance Computer Architecture (HPCA-27), Seoul, South Korea [retrieved May… [cited by applicant]
Kim, Yoongu et al., “A case for exploiting subarray-level parallelism (SALP) in DRAM”, 2012 39th Annual International Symposium on Computer Architecture (ISCA) [retrieved Sep. 15, 2022]. Retrieved from the Internet <htt… [cited by applicant]
Kim, Yoongu et al., “Flipping bits in memory without accessing them: an experimental study of DRAM disturbance errors”, ACM SIGARCH Computer Architecture News, vol. 42, No. 3 [retrieved Sep. 15, 2022]. Retrieved from th… [cited by applicant]
Konoth, Radhesh Krishnan , “ZebRAM: Comprehensive and Compatible Software Protection Against Rowhammer Attacks”, 13th USENIX Symposium on Operating Systems Design and Implementation [retrieved Sep. 15, 2022]. Retrieved … [cited by applicant]
Kotra, Jagadish B. et al., “Pursuant to MPEP § 2001.06(b) the applicant brings the following co-pending application to the Examiner's attention:”, U.S. Appl. No. 18/146,509, filed Dec. 27, 2022, 48 pages. [cited by applicant]
Lamport, Leslie , “Sharing Memory Between Processes”, Part II. Interprocess Communication [retrieved May 24, 2023]. Retrieved from the Internet <https://techpubs.jurassic.nl/manuals/0630/developer/T_IRIX_Prog/sgi_html/c… [cited by applicant]
Lee, Chulki et al., “DRAM Row hammer micro-benchmark”, GitHub, Inc. Uploaded by rowhammer-test [retrieved Sep. 15, 2022]. Retrieved from the Internet <https://github.com/google/rowhammer-test>., 3 Pages. [cited by applicant]
Lee, Eojin et al., “TWiCe: preventing row-hammering by exploiting time window counters”, Proceedings of the 46th International Symposium on Computer Architecture [retrieved Sep. 15, 2022]. Retrieved from the Internet <h… [cited by applicant]
Orosa, Lois et al., “A Deeper Look into RowHammer's Sensitivities: Experimental Analysis of Real DRAM Chips and Implications on Future Attacks and Defenses”, Cornell University arXiv, arXiv.org [retrieved Sep. 15, 2022]… [cited by applicant]
Qureshi, Moinuddin et al., “Hydra: enabling low-overhead mitigation of row-hammer at ultra-low thresholds via hybrid tracking”, Proceedings of the 49th Annual International Symposium on Computer Architecture [retrieved … [cited by applicant]
Saileshwar, Gururaj , “Randomized row-swap: mitigating Row Hammer by breaking spatial correlation between aggressor and victim rows”, Proceedings of the 27th ACM International Conference on Architectural Support for Pro… [cited by applicant]
Yaǧlikçl, Giray A. et al., “BlockHammer: Preventing RowHammer at Low Cost by Blacklisting Rapidly-Accessed DRAM Rows”, Cornell University arXiv, arXiv.org [retrieved Sep. 15, 2022]. Retrieved from the Internet <https://… [cited by applicant]
U.S. Appl. No. 17/136,767 , “Non-Final Office Action”, U.S. Appl. No. 17/136,767, filed Dec. 20, 2023, 20 pages. [cited by applicant]
Ahn, Junwhan , et al., “PIM-enabled instructions: a low-overhead, locality-aware processing-in-memory architecture”, ACM SIGARCH Computer Architecture News, vol. 43, No. 3S [retrieved Jan. 12, 2024]. Retrieved from the … [cited by applicant]
Byoung-Hak, Kim , et al., “Exploration of a PIM Design Configuration for Energy-Efficient Task Offloading”, 2019 IEEE International Symposium on Circuits and Systems (ISCAS) [retrieved Jan. 12, 2024]. Retrieved from the… [cited by applicant]
Ghose, S , et al., “Processing-in-memory: A workload-driven perspective”, IBM Journal of Research and Development, vol. 63, No. 6 [retrieved Jan. 12, 2024]. Retrieved from the Internet <https://doi.org/10.1147/JRD.2019.… [cited by applicant]
Ghose, S, et al., “Processing-in-memory: A workload-driven perspective”, IBM Journal of Research and Development, vol. 63, No. 6 [retrieved Jan. 12, 2024-]. Retrieved from the Internet <https://doi.org/10.1147/JRD.2019.… [cited by applicant]
Lee, Won Jun , et al., “Design of Processing—“Inside”—Memory Optimized for DRAM Behaviors”, IEEE Access, vol. 7 [retrieved Jan. 12, 2024]. Retrieved from the Internet <https://doi.org/10.1109/ACCESS.2019.2924240>, Jun. … [cited by applicant]
Pattnaik, Ashutosh , et al., “Scheduling techniques for GPU architectures with processing-in-memory capabilities”, PACT '16: Proceedings of the 2016 International Conference on Parallel Architectures and Compilation [re… [cited by applicant]
“Final Office Action”, U.S. Appl. No. 17/473,242, filed Oct. 22, 2024, 13 pages. [cited by applicant]
“Final Office Action”, U.S. Appl. No. 18/298,723, filed Oct. 11, 2024, 7 pages. [cited by applicant]
“Non-Final Office Action”, U.S. Appl. No. 18/374,951, filed Nov. 7, 2024, 10 pages. [cited by applicant]
“Corrected Notice of Allowability”, U.S. Appl. No. 18/374,969, filed Jan. 15, 2025, 2 pages. [cited by applicant]
“Notice of Allowance”, U.S. Appl. No. 18/374,969, filed Jan. 2, 2025, 10 pages. [cited by applicant]
U.S. Appl. No. 18/393,657 , “Notice of Allowance”, U.S. Appl. No. 18/393,657, filed Jul. 31, 2024, 9 pages. [cited by applicant]
“Notice of Allowance”, U.S. Appl. No. 17/853,613, filed Apr. 1, 2025, 6 pages. [cited by applicant]
“Non-Final Office Action”, U.S. Appl. No. 18/298,723, filed Mar. 19, 2025, 9 pages. [cited by applicant]
“Final Office Action”, U.S. Appl. No. 18/374,951, filed May 8, 2025, 11 pages. [cited by applicant]
“Non-Final Office Action”, U.S. Appl. No. 17/473,242, filed Jun. 24, 2025, 15 pages. [cited by applicant]
“Non-Final Office Action”, U.S. Appl. No. 18/192,925, filed Aug. 26, 2025, 23 pages. [cited by applicant]
“Non-Final Office Action”, U.S. Appl. No. 18/374,951, filed Aug. 27, 2025, 11 pages. [cited by applicant]
“Corrected Notice of Allowability”, U.S. Appl. No. 18/621,319, filed Aug. 4, 2025, 2 pages. [cited by applicant]
“Notice of Allowance”, U.S. Appl. No. 18/621,319, filed Jun. 18, 2025, 13 pages. [cited by applicant]
“Notice Of Allowance”, U.S. Appl. No. 18/298,723, filed Aug. 13, 2025; 8 pages. [cited by applicant]
Final Office Action issued in U.S. Appl. No. 18/192,925, mailed Jan. 27, 2026, 25 pages. [cited by applicant]