On Wed, 2019-03-20 at 08:08 -0700, Bart Van Assche wrote: > On Tue, 2019-03-19 at 16:41 +0200, Maxim Levitsky wrote: > > * Polling kernel thread is used. The polling is stopped after a > > predefined timeout (1/2 sec by default). > > Support for all interrupt driven mode is planned, and it shows promising > > results. > > Which cgroup will the CPU cycles used for polling be attributed to? Can the > polling code be moved into user space such that it becomes easy to identify > which process needs most CPU cycles for polling and such that the polling > CPU cycles are attributed to the proper cgroup? Currently there is a single IO thread per each virtual controller instance. I would prefer to keep all the driver in the kernel, but I think I can make it cgroup aware, in a simiar way this is done in vhost-net, and vhost-scsi. Best regards, Maxim Levitsky > Thanks, > > Bart.
