[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5bw7yc6bacojk2i2ikhlmf2skfiix6t3ipchbnvyfttmyh644j@iyquxeuyapd7>
Date: Wed, 5 Mar 2025 11:12:21 +0100
From: Michal Koutný <mkoutny@...e.com>
To: Tejun Heo <tj@...nel.org>
Cc: Waiman Long <llong@...hat.com>, cgroups@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, Josef Bacik <josef@...icpanda.com>,
Jens Axboe <axboe@...nel.dk>, Johannes Weiner <hannes@...xchg.org>
Subject: Re: [PATCH 1/9] cgroup/cpuset-v1: Add deprecation warnings to
sched_load_balance and memory_pressure_enabled
On Tue, Mar 04, 2025 at 08:04:06AM -1000, Tejun Heo <tj@...nel.org> wrote:
> I'm apprehensive about adding warning messages which may be triggered
> consistently without anything end users can do about them.
That means you'd distinguish RE (replacement exists) vs DN (dropped as
non-ideal) categories?
> I think that deprecation messages, unless such deprecation is
> immediate and would have direct consequences on how the system can be
> used, should be informational.
I could subscribe to that if there weren't so many other places to
evaluate:
$ git grep -i "pr_warn.*deprec" torvalds/master -- | wc -l
62
$ git grep -i "pr_info.*deprec" torvalds/master -- | wc -l
2
So is the disctinction worth the hassle?
Michal
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists