Hello, On Sat, Jan 07, 2023 at 02:07:38AM +0800, hanjinke wrote: > In our internal scenario, iocost has been deployed as the main io isolation > method and is gradually spreading。 Ah, glad to hear. If you don't mind sharing, how are you configuring iocost currently? How do you derive the parameters? > But for some specific scenarios with old kernel versions, blk-throtl > is alose needed. The scenario described in my email is in the early stage of Yeah, I think we use blk-throttle in very limited cases currently but might need to deploy hard limits more in the future. > research and extensive testing for it. During this period，some priority > inversion issues amoug cgroups or within one cgroup have been observed. So I > send this patch to try to fix or mitigate some of these issues. blk-throttle has a lot of issues which may be difficult to address. Even the way it's configured is pretty difficult to scale across different hardware / application combinations and we've neglected its control performance and behavior (like handling of shared IOs) for quite a while. While iocost's work-conserving control does address a lot of the use cases we see today, it's likely that we'll need hard limits more in the future too. I've been thinking about implementing io.max on top of iocost. There are some challenges around dynamic vrate adj semantics but it's kinda attractive because iocost already has the concept of total device capacity. Thanks. -- tejun
