all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Matt Corallo <lpxdfsfs@mattcorallo.com>, pve-devel@lists.proxmox.com
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH] Update cpu.weight default to match documented default
Date: Wed, 24 Aug 2022 10:26:01 +0200	[thread overview]
Message-ID: <0342b548-cfb0-0737-2f1d-310b14291680@proxmox.com> (raw)
In-Reply-To: <837ccb7a-a073-09ac-f4ab-708b797d41b1@bluematt.me>

Am 24.08.22 um 01:56 schrieb Matt Corallo:
> 
> 
> On 8/19/22 6:08 AM, Fiona Ebner wrote:
>> Hi,
>>
>> On 16.08.22 05:49, Matt Corallo wrote:
>>> Proxmox documentation describes the default CPU weight as 1024 in
>>> numerous places. However, when unset, the Linux default CGROUP
>>> weight is 100.
>>>
>>
>> I'd rather update the documentation in all places, because most likely
>> it just wasn't adapted to mention the cgroup2 default yet. Some places
>> already do mention both defaults, e.g. 'man 5 qm.conf'
> 
> Hmm, am I understanding that correctly that now I have to figure out if
> I'm using cgroup2 or cgroup1 to figure out if the default is 1024 or
> 100? Or are modern PVE's all running cgroup2 and the UI simply needs to
> be updated universally to say that the default is now 100?
> 
> Matt
> 

PVE 7.x uses cgroupv2 by default, so reporting the new default in the UI
would be correct for most installations. That said, we do still support
cgroupv1[0], so ideally, the default in the UI would be shown depending
on the cgroup version the node is actually running.

I think this was the plan, but it never got realized. This (not yet
applied) patch[1] would expose the cluster node's cgroup version to
other nodes, to be used by the frontend.

@Thomas: Is this still the plan? If it is, I'll cook up a v2 adding UI
and doc patches.

[0] https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#CGroupV2
[1] https://lists.proxmox.com/pipermail/pve-devel/2021-July/049253.html




  parent reply	other threads:[~2022-08-24  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a5789fb9-b22a-a58a-9190-fa34e89c41a2@bluematt.me>
2022-08-19 10:01 ` Fiona Ebner
2022-08-19 10:03   ` Fiona Ebner
2022-08-19 10:08 ` Fiona Ebner
     [not found]   ` <837ccb7a-a073-09ac-f4ab-708b797d41b1@bluematt.me>
2022-08-24  8:26     ` Fiona Ebner [this message]
2022-09-02  6:33       ` Thomas Lamprecht

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=0342b548-cfb0-0737-2f1d-310b14291680@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=lpxdfsfs@mattcorallo.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal