I opened an issue in line with the new kdereview process
https://invent.kde.org/libraries/kcgroups/-/issues/1
Jonathan
On Sat, 21 Nov 2020 at 00:38, Albert Astals Cid wrote:
> El divendres, 20 de novembre de 2020, a les 14:55:16 CET, Henri Chain va
> escriure:
> > Hello everyone,
> >
> >
Hello,
On Tuesday, 2 March 2021 12:06:51 CET David Edmundson wrote:
> > > (where 1000 is of course dynamic)
> >
> > Ditto, what enum names could we give to those?
>
> / -> All
> /system.slice -> System
> user.slice/user-1000.slice/user@1000.service -> User
>
> > (where 1000 is of course dynamic)
>
> Ditto, what enum names could we give to those?
/ -> All
/system.slice -> System
user.slice/user-1000.slice/user@1000.service -> User
user.slice/user-1000.slice/user@1000.service/app.slice -> UserApps
On Sunday, 13 December 2020 22:41:24 CET David Edmundson wrote:
> On Thu, Dec 3, 2020 at 11:48 AM Kevin Ottens wrote:
> > Hello,
> >
> > On Thursday, 3 December 2020 12:15:52 CET David Edmundson wrote:
> > > Ultimately this isn't really dealing with cgroups directly but with
> > > the manager to
On Thu, Dec 3, 2020 at 11:48 AM Kevin Ottens wrote:
>
> Hello,
>
> On Thursday, 3 December 2020 12:15:52 CET David Edmundson wrote:
> > Ultimately this isn't really dealing with cgroups directly but with
> > the manager to control them, systemd.
> >
> > That's correct usage, kernel docs of
On Thu, Dec 3, 2020 at 12:48 PM Kevin Ottens wrote:
>
> Good point. Got a similar question though, which other unit types would be
> useful to control? Reason being that API wise I'd smell an enum for something
> like this.
>
Well if this library would evolve towards C++ API for interacting with
Hello,
On Thursday, 3 December 2020 12:15:52 CET David Edmundson wrote:
> Ultimately this isn't really dealing with cgroups directly but with
> the manager to control them, systemd.
>
> That's correct usage, kernel docs of cgroups say to go via a
> controller for write operations. However that
Ultimately this isn't really dealing with cgroups directly but with
the manager to control them, systemd.
That's correct usage, kernel docs of cgroups say to go via a
controller for write operations. However that at point is it worth
naming the library ksystemd?
It might cause some contention due
Hello,
On Friday, 20 November 2020 14:55:16 CET Henri Chain wrote:
> KCgroups has been moved to KDEReview !
> What is that, you ask ? It's a library that wraps the systemd dbus API to
> expose a higher-level concept of desktop application and allow control of
> its system resource usage (CPU,
On Saturday, November 21, 2020 1:38:47 AM CET Albert Astals Cid wrote:
> El divendres, 20 de novembre de 2020, a les 14:55:16 CET, Henri Chain va
escriure:
> > Hello everyone,
> >
> > KCgroups has been moved to KDEReview !
> > What is that, you ask ? It's a library that wraps the systemd dbus
On Friday, November 20, 2020 8:29:33 PM CET Jacky Alcine wrote:
> This is exciting! Is it needed to explicitly put "cgroups" in the name?
> (What I'm really asking is if there's a way to have this work in a
> cross-platform way)
Yes, this library takes advantage of cgroups resource control, and
El divendres, 20 de novembre de 2020, a les 14:55:16 CET, Henri Chain va
escriure:
> Hello everyone,
>
> KCgroups has been moved to KDEReview !
> What is that, you ask ? It's a library that wraps the systemd dbus API to
> expose a higher-level concept of desktop application and allow control of
This is exciting! Is it needed to explicitly put "cgroups" in the name? (What
I'm really asking is if there's a way to have this work in a cross-platform way)
On Fri, Nov 20, 2020, at 05:55, Henri Chain wrote:
> Hello everyone,
>
> KCgroups has been moved to KDEReview !
> What is that, you ask
Hello everyone,
KCgroups has been moved to KDEReview !
What is that, you ask ? It's a library that wraps the systemd dbus API to
expose a higher-level concept of desktop application and allow control of its
system resource usage (CPU, RAM, IO, etc).
It relies on the recent ability of plasma to
14 matches
Mail list logo
