lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 22 Nov 2010 11:54:40 +0530 From: Balbir Singh <balbir@...ux.vnet.ibm.com> To: Lennart Poettering <mzxreary@...inter.de> Cc: Ben Gamari <bgamari.foss@...il.com>, Linus Torvalds <torvalds@...ux-foundation.org>, David Miller <davem@...emloft.net>, tytso@....edu, a.p.zijlstra@...llo.nl, debiandev@...il.com, alan@...rguk.ukuu.org.uk, dhaval.giani@...il.com, efault@....de, vgoyal@...hat.com, oleg@...hat.com, markus@...ppelsdorf.de, mathieu.desnoyers@...icios.com, mingo@...e.hu, linux-kernel@...r.kernel.org Subject: Re: [RFC/RFT PATCH v3] sched: automated per tty task groups * Lennart Poettering <mzxreary@...inter.de> [2010-11-20 16:41:01]: > On Sat, 20.11.10 09:55, Balbir Singh (balbir@...ux.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@...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