From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Levitsky Subject: Re: [PATCH 0/9] RFC: NVME VFIO mediated device Date: Wed, 20 Mar 2019 18:48:17 +0200 Message-ID: References: <20190319144116.400-1-mlevitsk@redhat.com> <1553094528.65329.29.camel@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Fam Zheng , Keith Busch , Sagi Grimberg , kvm@vger.kernel.org, "David S . Miller" , Greg Kroah-Hartman , Liang Cunming , Wolfram Sang , linux-kernel@vger.kernel.org, Kirti Wankhede , Jens Axboe , Alex Williamson , John Ferlan , Mauro Carvalho Chehab , Paolo Bonzini , Liu Changpeng , "Paul E . McKenney" , Amnon Ilan , Christoph Hellwig , Nicolas Ferre To: Bart Van Assche , linux-nvme@lists.infradead.org Return-path: In-Reply-To: <1553094528.65329.29.camel@acm.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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.