On 9/5/24 11:05 AM, Linus Walleij wrote:
For Androids and chromebooks it keeps the device interactive during heavy disk (eMMC) activity, such as when Android updates a pile of apps (.apk files).
Is that issue perhaps specific to eMMC devices? I have never seen an Android device with UFS storage becoming unresponsive during app updates. Additionally, now that the mq-deadline I/O scheduler supports I/O priorities, it is easy to give foreground I/O a higher priority in Android than background I/O. All that is needed is to add something like the following in an .rc file that is executed during boot: write /dev/blkio/blkio.prio.class promote-to-rt Bart.
