public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31049] Feature request: posix_spawnattr_setrlimit_np()
Date: Tue, 14 Nov 2023 20:55:32 +0000	[thread overview]
Message-ID: <bug-31049-131-qIgjHG6Ajs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31049-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31049

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
I think this would make sense, especially to set up the maximum limits of some
resources.  The next glibc 2.39 will provide a way to set up a new process with
a different cgroupv2 (posix_spawnattr_getcgroup_np,
posix_spawnattr_setcgroup_np), which allows fine-tuning the process constrain
resources through the Linux API. However, the cgroupsv2 might require
additional setup and are more complex.

Could you check if the API provided with this WIP patch would fit the
requirements [1]?

[1] https://github.com/zatrazz/glibc/tree/azanella/bz31049-spawn-setresource

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2023-11-14 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 21:51 [Bug libc/31049] New: " tavianator at tavianator dot com
2023-11-14 20:55 ` adhemerval.zanella at linaro dot org [this message]
2023-11-14 21:03 ` [Bug libc/31049] " tavianator at tavianator dot com
2023-11-15 12:52 ` adhemerval.zanella at linaro dot org
2023-11-15 13:12 ` adhemerval.zanella at linaro dot org
2023-11-15 13:49 ` tavianator at tavianator dot com

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=bug-31049-131-qIgjHG6Ajs@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).