[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56DBEC64.6090805@mellanox.com>
Date: Sun, 6 Mar 2016 10:37:56 +0200
From: Haggai Eran <haggaie@...lanox.com>
To: Parav Pandit <pandit.parav@...il.com>, Tejun Heo <tj@...nel.org>
CC: <cgroups@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
<lizefan@...wei.com>, Johannes Weiner <hannes@...xchg.org>,
Doug Ledford <dledford@...hat.com>,
Liran Liss <liranl@...lanox.com>,
"Hefty, Sean" <sean.hefty@...el.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Jonathan Corbet <corbet@....net>, <james.l.morris@...cle.com>,
<serge@...lyn.com>, Or Gerlitz <ogerlitz@...lanox.com>,
Matan Barak <matanb@...lanox.com>, <akpm@...ux-foundation.org>,
<linux-security-module@...r.kernel.org>
Subject: Re: [PATCHv9 1/3] rdmacg: Added rdma cgroup controller
On 05/03/2016 19:20, Parav Pandit wrote:
>> > 3 is fine but resource [un]charging is not hot path?
> charge/uncharge is hot path from cgroup perspective.
Most of the resources the RDMA cgroup handles are only allocated at
the beginning of the application. The RDMA subsystem allows direct
user-space access to the devices, so most of the hot path operations
don't go through the kernel at all.
It is true though that for some applications MR registration and
de-registration is in the hot path.
Haggai
Powered by blists - more mailing lists