[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20151117.162554.314531574043190960.davem@davemloft.net>
Date: Tue, 17 Nov 2015 16:25:54 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: tj@...nel.org
Cc: pablo@...filter.org, kaber@...sh.net, kadlec@...ckhole.kfki.hu,
lizefan@...wei.com, hannes@...xchg.org, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com, daniel@...earbox.net,
daniel.wagner@...-carit.de, nhorman@...driver.com
Subject: Re: [PATCH 4/5] sock, cgroup: add sock->sk_cgroup
From: Tejun Heo <tj@...nel.org>
Date: Tue, 17 Nov 2015 14:40:39 -0500
> In preparation, this patch adds sock->sk_cgroup which points to the
> associated cgroup. A sock is associated on creation and stays
> associated to the same cgroup until freed; unfortunately, this ends up
> adding another cgroup field to struct sock on top of sk_cgrp_prioidx
> and sk_classid. I tried to think of a way to somehow overload the
> existing fields but couldn't come up with a reasonable one.
sk->sk_cgrp_prioidx is simply sk->sk_cgroup->id, is it not?
We really need to consolidate this before we stuff even more members
into the socket for control group support, sorry.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists