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: Wed, 13 Feb 2008 10:27:49 +0100 From: Peter Zijlstra <a.p.zijlstra@...llo.nl> To: Hiroshi Shimamoto <h-shimamoto@...jp.nec.com> Cc: mingo@...e.hu, linux-kernel@...r.kernel.org Subject: Re: [RFC PATCH] RTTIME watchdog timer proc interface On Tue, 2008-02-12 at 14:21 -0800, Hiroshi Shimamoto wrote: > Peter Zijlstra wrote: > > On Mon, 2008-02-11 at 13:44 -0800, Hiroshi Shimamoto wrote: > >> Hi Ingo, > >> > >> I think an interface to access RLIMIT_RTTIME from outside is useful. > >> It makes administrator able to set RLIMIT_RTTIME watchdog to existing > >> real-time applications without impact. > >> > >> I implemented that interface with /proc filesystem. > > > > /proc/<pid>/tasks/<tid>/rttime might also make sense. > > > thanks, I'll add. I just realized that because its an rlimit, we store these values process-wide. The per task thing was a feature request from someone, and I just jumped on your interface without proper consideration. I'll need to think a bit more on this -- 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