Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753706Ab0KTPlY (ORCPT ); Sat, 20 Nov 2010 10:41:24 -0500 Received: from tango.0pointer.de ([85.214.72.216]:39406 "EHLO tango.0pointer.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752256Ab0KTPlX (ORCPT ); Sat, 20 Nov 2010 10:41:23 -0500 Date: Sat, 20 Nov 2010 16:41:01 +0100 From: Lennart Poettering To: Balbir Singh Cc: Ben Gamari , Linus Torvalds , David Miller , tytso@mit.edu, a.p.zijlstra@chello.nl, debiandev@gmail.com, alan@lxorguk.ukuu.org.uk, dhaval.giani@gmail.com, efault@gmx.de, vgoyal@redhat.com, oleg@redhat.com, markus@trippelsdorf.de, mathieu.desnoyers@efficios.com, mingo@elte.hu, linux-kernel@vger.kernel.org Subject: Re: [RFC/RFT PATCH v3] sched: automated per tty task groups Message-ID: <20101120154100.GA25803@tango.0pointer.de> References: <20101119.082944.226775934.davem@davemloft.net> <20101119163430.GA12353@tango.0pointer.de> <20101119.084302.71115175.davem@davemloft.net> <87mxp53z72.fsf@gmail.com> <20101120011330.GB4183@tango.0pointer.de> <20101120042557.GA12043@balbir.in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101120042557.GA12043@balbir.in.ibm.com> Organization: Red Hat, Inc. X-Campaign-1: () ASCII Ribbon Campaign X-Campaign-2: / Against HTML Email & vCards - Against Microsoft Attachments User-Agent: Leviathan/19.8.0 [zh] (Cray 3; I; Solaris 4.711; Console) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1399 Lines: 31 On Sat, 20.11.10 09:55, Balbir Singh (balbir@linux.vnet.ibm.com) wrote: > > However, I am not sure I like the idea of having pollable files like that, > > because in the systemd case I am very much interested in getting > > recursive notifications, i.e. I want to register once for getting > > notifications for a full subtree instead of having to register for each > > cgroup individually. > > > > My personal favourite solution would be to get a netlink msg when a > > cgroup runs empty. That way multiple programs could listen to the events > > at the same time, and we'd have an easy way to subscribe to a whole > > hierarchy of groups. > > The netlink message should not be hard to do if we agree to work on > it. The largest objections I've heard is that netlink implies > network programming and most users want to be able to script in > their automation and network scripting is hard. Well, the notify_on_release stuff cannot be dropped anyway at this point in time, so netlink support would be an addition to, not a replacement for the current stuff that might be useful for scripting folks. Lennart -- Lennart Poettering - Red Hat, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/