Messages in this thread | | | Date | Thu, 11 Sep 2008 01:45:23 +0200 | From | Thomas Graf <> | Subject | Re: [PATCH 1/2] Traffic control cgroups subsystem |
| |
* Paul Menage <menage@google.com> 2008-09-10 16:31 > Yes, for this particular case it doesn't work. But isn't it much more > likely that the admin/user will know that web-browsers tend to trigger > bulk data transfers and configure the system so that the web browser > always starts in its own cgroup, rather than trying to jump on it > after the fact?
That's argueable I guess. Likely or not, it doesn't make sense to add such restrictions if not required, especially not when it is trivial to just look at the cgroup of the task directly.
If the ingress case is of such importance, I'd propose to lookup the classid via skb -> socket -> task -> classid.
Anyways, I think we've listed all the pros and cons of either approach.
| |