patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Dhaval Giani <dhaval.giani@gmail.com>
To: Demi Marie Obenour <demiobenour@gmail.com>,
	Tom James Hromatka <tom.hromatka@oracle.com>,
	Kamalesh Babulal <bkamalesh5@gmail.com>
Cc: Linux cgroups development <cgroups@vger.kernel.org>,
	Alyssa Ross <hi@alyssa.is>,
	Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: Implementing a control group manager that isn't a persistent daemon
Date: Mon, 13 Jul 2026 19:56:13 -0700	[thread overview]
Message-ID: <CAPhKKr-WAzqjFuV=cXP5uggJGdVUi6=VQ82J5q90Ti_wUmSS=g@mail.gmail.com> (raw)
In-Reply-To: <d83a6cc2-73bf-46fd-9ec2-abd667828d6e@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

On Sun, Jul 12, 2026 at 3:51 PM Demi Marie Obenour <demiobenour@gmail.com>
wrote:

> Hello!
>
> I'm currently implementing a control group manager that isn't a
> persistent daemon.  Instead, it's a command-line tool.  The system
> I'm working on uses s6 instead of systemd, and s6 doesn't have native
> control group support.
>
> The current plan is to offer a few options:
>
> 1. Create a cgroup if it doesn't exist.  If it does, wait for it to
>    be empty.  Then execute a program in that cgroup.
>
> 2. Create a program in a cgroup, without waiting for the cgroup to
>    be empty.
>
> 2. Kill all programs in a cgroup.
>
>
Why can libcgroup not do the same for you?

Dhaval


> Unfortunately, I'm not able to wait for a cgroup to become empty.
> I don't seem to be getting EPOLLPRI or EPOLLERR events.  What
> is the proper way to get those events?  Is there a kernel version
> with a bug in this area?
> --
> Sincerely,
> Demi Marie Obenour (she/her/hers)
>
>
>

[-- Attachment #2: Type: text/html, Size: 1620 bytes --]

      reply	other threads:[~2026-07-15  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12 22:50 Implementing a control group manager that isn't a persistent daemon Demi Marie Obenour
2026-07-14  2:56 ` Dhaval Giani [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPhKKr-WAzqjFuV=cXP5uggJGdVUi6=VQ82J5q90Ti_wUmSS=g@mail.gmail.com' \
    --to=dhaval.giani@gmail.com \
    --cc=bkamalesh5@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=demiobenour@gmail.com \
    --cc=devel@spectrum-os.org \
    --cc=hi@alyssa.is \
    --cc=tom.hromatka@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).