On 7/13/23 11:58?AM, Tejun Heo wrote: > It's a bit out of scope for this patchset but I think it might make > sense to build a timestamp caching infrastructure. The cached > timestamp can be invalidated on context switches (block layer already > hooks into them) and issue and other path boundaries (e.g. at the end > of plug flush). This is a great idea! Have the plug init start with the timestamp invalid, and use some blk_get_time() helpers that return the time for no plug, and set it in the plug if not set. Flushing the plug would mark it invalid again. This obviously won't help the no plugging cases, but those are not that interesting in comparison. -- Jens Axboe
