docs/designs/phosphor-hwmon-io-uring.md

16 therefore may block other functions such as IPMI. This project will involve
38 By using io_uring, the asynchronous sensor reads will need to maintain the same
40 OpenBMC repositories that will benefit from this library include:
51 Users will need the ability to choose whether they want to utilize this new
54 io_uring library will need to be calculated for each daemon.
58 In the phosphor-hwmon repository, the primary files that will require
69 The refactor will maintain this loop over all sensors, but instead make the read
70 operation non-blocking by using an io_uring wrapper. A caching layer will be
71 used to store the read results, which will be the main access point for
114 sensor), users will be able to determine whether or not to utilize this new
125 Each call to access the read value of a particular sesnor in the read cache will
126 not only return the cached value but will also submit a SQE (submission queue
127 event) to io_uring for that sensor; this SQE acts as a read request that will be
130 do not get submitted and overlap; the set entries will be cleared upon
132 CQE will then be processed, and its information will update the cache map.
136 sensor reads in the synchronous implementation. The kernel will process these
137 requests, and before the next iteration of sensor reads the cache will attempt
140 Simply put, an access to some "Sensor A" in the read cache will create an
154 For these primary reasons, the native AIO library will not be considered for
162 arbitrary than latency profiling). These performance changes will have to be
165 There will be no security impact.
169 The change will utilize the gTest framework to ensure the original functionality