Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751365Ab0KVGYs (ORCPT ); Mon, 22 Nov 2010 01:24:48 -0500 Received: from e8.ny.us.ibm.com ([32.97.182.138]:33307 "EHLO e8.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751154Ab0KVGYr (ORCPT ); Mon, 22 Nov 2010 01:24:47 -0500 Date: Mon, 22 Nov 2010 11:54:40 +0530 From: Balbir Singh To: Lennart Poettering 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: <20101122062440.GF12043@balbir.in.ibm.com> Reply-To: balbir@linux.vnet.ibm.com 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> <20101120154100.GA25803@tango.0pointer.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20101120154100.GA25803@tango.0pointer.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1630 Lines: 36 * Lennart Poettering [2010-11-20 16:41:01]: > 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. Agreed, we still need the old notify_on_release. Are you suggesting that for scripting we use the old interface and newer tools use netlink? -- Three Cheers, Balbir -- 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/