On Thu, Oct 14, 2021 at 11:29:38AM +0200, Michal Koutný wrote: > On Thu, Oct 14, 2021 at 10:38:30AM +0200, Odin Hultgren van der Horst <odin@xxxxxxxxxxxxxxxx> wrote: > > On Mon, Oct 11, 2021 at 05:34:16PM +0200, Michal Koutný wrote: > > > What do you want to achieve actually? > > If a application use a thread per client that is connected, and a client > > decides to do a large read on a io device it will cause all other clients > > to be starved of io. I want to avoid this. > > IIUC, the application would have to be collaborative anyway (dividing > threads into cgroups) and given you're concered about reads, > set_ioprio(2) might be enough for this case. > > Also, if you've seen starvation (likely depends on IO scheduler), you > may raise this with linux-block ML. > > HTH, > Michal I also want to be able to limit amount of io for a given thread, just like you could to with io.max. So a given client cant just use all my io even though there is no competing thread. Thanks, Odin
