From: Tejun Heo <tj@kernel.org>
To: Parav Pandit <pandit.parav@gmail.com>
Cc: cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
lizefan@huawei.com, hannes@cmpxchg.org, dledford@redhat.com,
liranl@mellanox.com, sean.hefty@intel.com,
jgunthorpe@obsidianresearch.com, haggaie@mellanox.com,
corbet@lwn.net, james.l.morris@oracle.com, serge@hallyn.com,
ogerlitz@mellanox.com, matanb@mellanox.com,
akpm@linux-foundation.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCHv11 3/3] rdmacg: Added documentation for rdmacg
Date: Wed, 24 Aug 2016 17:18:24 -0400 [thread overview]
Message-ID: <20160824211824.GW8185@htj.duckdns.org> (raw)
In-Reply-To: <1471869231-15576-4-git-send-email-pandit.parav@gmail.com>
On Mon, Aug 22, 2016 at 06:03:51PM +0530, Parav Pandit wrote:
> + rdma.max
> + A readwrite file that exists for all the cgroups except root that
Can you please add that it's a nested-keyed file?
...
> + rdma.current
> + A read-only file that describes current resource usage.
Ditto.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-08-24 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:33 [PATCHv11 0/3] rdmacg: IB/core: rdma controller support Parav Pandit
2016-08-22 12:33 ` [PATCHv11 1/3] rdmacg: Added rdma cgroup controller Parav Pandit
2016-08-22 12:33 ` [PATCHv11 2/3] IB/core: added support to use " Parav Pandit
2016-08-22 12:33 ` [PATCHv11 3/3] rdmacg: Added documentation for rdmacg Parav Pandit
2016-08-24 21:18 ` Tejun Heo [this message]
2016-08-24 22:55 ` Rami Rosen
2016-08-25 7:58 ` Parav Pandit
2016-08-24 21:17 ` [PATCHv11 0/3] rdmacg: IB/core: rdma controller support Tejun Heo
2016-08-25 7:32 ` Christoph Hellwig
2016-08-25 8:00 ` Parav Pandit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160824211824.GW8185@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=hannes@cmpxchg.org \
--cc=james.l.morris@oracle.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liranl@mellanox.com \
--cc=lizefan@huawei.com \
--cc=matanb@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=pandit.parav@gmail.com \
--cc=sean.hefty@intel.com \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox