Effective avoidance of line cache misses
A system includes a line cache, a memory device, and a processing device to execute firmware to detect that a received event is located in an events list, wherein events stored in the events list are associated with critical functions that occur no more than once per a threshold number of days and time out after between 15 microseconds and a predetermined number of hundreds of seconds. The firmware is further to enable access to the line cache and execute a critical function associated with the received event out of an always-loaded area of the line cache.
1. A system comprising:
a line cache;
a memory device; and
a processing device operatively coupled to the line cache and the memory device, the processing device to execute firmware to:
detect that a received event is located in an events list, wherein events stored in the events list are associated with critical functions that occur no more than once per a threshold number of days and time out after between 15 microseconds and a predetermined number of hundreds of milliseconds;
enable access to the line cache; and
execute a critical function associated with the received event out of an always-loaded area of the line cache.
2. The system of claim 1 , wherein the processing device is further to, at startup of the system, preload the critical functions into the always-loaded area of the line cache.
3. The system of claim 1 , wherein the always-loaded area of the line cache is approximately two kilobytes in size.
4. The system of claim 1 , wherein the events list comprises two or more of: multiple logging events, a sanitize command, a smart command transport command, a write uncorrectable command, a download firmware command, and a trim command.
5. The system of claim 1 , wherein the critical function comprises one of a drive boot up sequence-related function, a sanitize handle function, a smart command transport function, a write uncorrectable handle function, a firmware image download function, or a trim handle function.
6. The system of claim 1 , wherein the processing device is further to:
detect termination of execution of pending critical functions;
disable access to the line cache; and
transition back to executing firmware instructions out of the memory device.
7. A system comprising:
a line cache;
a memory device; and
a processing device operatively coupled to the line cache and the memory device, the processing device to execute a manual function swap engine to, in response to being directed to execute a critical function, of a plurality of critical functions, that is not present in the line cache:
evict any data from a plurality of lines of an always-on area of the line cache; and
read a first number of bytes of each line partition of the critical function from the memory device into respective lines of the plurality of lines of the always-on area of the line cache; and
wherein the processing device is further to execute firmware to allow execution of the critical function out of the line cache after the plurality of lines of the line cache have been fully loaded by line cache hardware.
8. The system of claim 7 , wherein each critical function of the plurality of critical functions occurs no more than once per a threshold number of days and times out after between 15 microseconds and a predetermined number of hundreds of milliseconds.
9. The system of claim 7 , wherein the processing device is further to execute firmware to:
verify that a total size of the plurality of critical functions is greater than a size of the always-on area of the line cache; and
verify that the critical function is no larger than the size of the always-on area of the line cache.
10. The system of claim 7 , wherein the first number of bytes comprises four bytes and each line partition is 64-bytes in size.
11. The system of claim 7 , wherein the processing device is further to execute firmware to:
detect that a received event is located in an events list and is associated with the critical function; and
enable access to the line cache to handle execution of the critical function.
12. The system of claim 11 , wherein the processing device is further to:
detect termination of execution of pending critical functions;
disable the line cache; and
transition back to executing firmware instructions out of the memory device.
13. The system of claim 11 , wherein the events list comprises two or more of: multiple logging events, a sanitize command, a smart command transport command, a write uncorrectable command, a download firmware command, and a trim command.
14. The system of claim 7 , wherein the critical function comprises one of a drive boot up sequence-related function, a sanitize handle function, a smart command transport function, a write uncorrectable handle function, a firmware image download function, or a trim handle function.
15. A method comprising:
detecting, by a processing device of a memory sub-system controller, that a received event is located in an events lists, wherein events stored in the events list are associated with critical functions that occur no more than once per a threshold number of days and time out after between 15 microseconds and a predetermined number of hundreds of milliseconds;
enabling, by the processing device, access to a line cache coupled to the memory controller; and
in response to determining that a total size of the critical functions is less than or equal to a size of an always-on area of the line cache, executing a critical function associated with the received event out of an always-on area of the line cache.
16. The method of claim 15 , further comprising, at startup of the processing device, preloading the critical functions into the always-on area of the line cache such that the always-on area is always to store the critical functions.
17. The method of claim 15 , further comprising:
detecting termination of executing pending critical functions;
disabling access to the line cache; and
renewing execution of firmware instructions out of a memory device coupled to the processing device.
18. The method of claim 15 , further comprising, in response to determining that the total size of the critical functions is greater than the size of the always-on area of the line cache:
evicting, by a manual function swap engine, any data from a plurality of lines of the always-on area of the line cache;
reading, by the manual function swap engine, a first number of bytes of each line partition of the critical function from a memory device into respective lines of the plurality of lines of the always-on area of the line cache; and
allowing execution of the critical function out of the line cache after the plurality of lines of the line cache have been fully loaded by line cache hardware.
19. The method of claim 18 , further comprising verifying that each of the critical functions to be no larger than the size of the always-on area of the line cache.
20. The method of claim 18 , wherein the first number of bytes comprises four bytes and each line partition is 64-bytes in size.