util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: Benno Schulenberg <bensberg@telfort.nl>, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org,
	Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Subject: Re: [PATCH v2] chrt: Make priority optional for policies that don't use it
Date: Fri, 20 Jun 2025 11:03:05 +0530	[thread overview]
Message-ID: <0cb78aa7-4695-4b48-97f8-22dea3d9a697@linux.ibm.com> (raw)
In-Reply-To: <41499ee7-7d8f-4143-b560-1b02f2d1f00c@telfort.nl>

On 19/06/25 19:45, Benno Schulenberg wrote:
> 
> Op 18-06-2025 om 18:41 schreef Madadi Vineeth Reddy:
>> So, my thought is just to make priority argument optional for
>> policies that don't use it and keep the existing behavior as is.
> 
> That's not possible.  Currently, doing something like
> 
>   ./chrt --idle --pid $$
> 
> just reports the current policy and priority, and does
> not change the policy (because the priority is missing).
> After your patch, doing the same command reports nothing
> but _does_ change the policy.  You could still make it
> report the current settings, but that would give the
> wrong idea, because it would be the _old_ settings.
> 
> So, as Karel said, silently ignoring the policy option
> when no priority was given was ugly.  Too ugly to keep
> it that way.  As Karel implied: break compatibility and
> do the sensible thing: whenever a policy option is given,
> act upon it -- and when a needed priority is missing,
> error out.
> 

Sure, that makes sense. I will send a patch with these
changes accordingly.

Thanks,
Madadi Vineeth Reddy

> 
> Benno
> 


      reply	other threads:[~2025-06-20  5:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 18:24 [PATCH v2] chrt: Make priority optional for policies that don't use it Madadi Vineeth Reddy
2025-06-18  8:18 ` Benno Schulenberg
2025-06-18  9:18   ` Karel Zak
2025-06-18  9:25     ` Karel Zak
2025-06-18  9:34       ` Madadi Vineeth Reddy
2025-06-18 10:23         ` Madadi Vineeth Reddy
2025-06-18 10:45         ` Karel Zak
2025-06-18 16:33           ` Madadi Vineeth Reddy
2025-06-18  9:51     ` Madadi Vineeth Reddy
2025-06-18 12:29       ` Benno Schulenberg
2025-06-18 16:41         ` Madadi Vineeth Reddy
2025-06-19 14:15           ` Benno Schulenberg
2025-06-20  5:33             ` Madadi Vineeth Reddy [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=0cb78aa7-4695-4b48-97f8-22dea3d9a697@linux.ibm.com \
    --to=vineethr@linux.ibm.com \
    --cc=bensberg@telfort.nl \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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 NNTP newsgroup(s).