[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1553094528.65329.29.camel@acm.org>
Date: Wed, 20 Mar 2019 08:08:48 -0700
From: Bart Van Assche <bvanassche@....org>
To: Maxim Levitsky <mlevitsk@...hat.com>,
linux-nvme@...ts.infradead.org
Cc: Fam Zheng <fam@...hon.net>, Keith Busch <keith.busch@...el.com>,
Sagi Grimberg <sagi@...mberg.me>, kvm@...r.kernel.org,
"David S . Miller" <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Liang Cunming <cunming.liang@...el.com>,
Wolfram Sang <wsa@...-dreams.de>, linux-kernel@...r.kernel.org,
Kirti Wankhede <kwankhede@...dia.com>,
Jens Axboe <axboe@...com>,
Alex Williamson <alex.williamson@...hat.com>,
John Ferlan <jferlan@...hat.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Liu Changpeng <changpeng.liu@...el.com>,
"Paul E . McKenney" <paulmck@...ux.ibm.com>,
Amnon Ilan <ailan@...hat.com>, Christoph Hellwig <hch@....de>,
Nicolas Ferre <nicolas.ferre@...rochip.com>
Subject: Re: [PATCH 0/9] RFC: NVME VFIO mediated device
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?
Thanks,
Bart.
Powered by blists - more mailing lists