From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>,
'Paolo Valente' via bfq-iosched <bfq-iosched@googlegroups.com>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
Angelo Ruocco <angeloruocco90@gmail.com>,
lennart@poettering.net, mkoutny@suse.cz
Subject: Re: [PATCH 1/1] block, bfq: delete "bfq" prefix from cgroup filenames
Date: Mon, 8 Apr 2019 09:17:58 -0600 [thread overview]
Message-ID: <ef1481e8-c664-5f17-4a19-bb90daabc0b7@kernel.dk> (raw)
In-Reply-To: <5283A08F-FD6F-4A9C-841D-B49CE9B4CF1F@linaro.org>
On 4/8/19 9:14 AM, Paolo Valente wrote:
>
>
>> Il giorno 8 apr 2019, alle ore 17:08, Johannes Thumshirn <jthumshirn@suse.de> ha scritto:
>>
>> On Mon, Apr 08, 2019 at 09:05:19AM -0600, Jens Axboe wrote:
>>> I did consider that, and that would be doable. But honestly, I'm having a
>>> hard time seeing what issue we are attempting to fix by doing this.
>>
>> Yeah, I guess the real fix would be to update the documentation and the
>> expectations user-space has. Including eventual re-write of some udev rules or
>> whatever is facing these files. But to me that sounds more like a systemd or
>> even distro thing than a kernel thing.
>>
>
> Unfortunately the user-space people I have interacted with find crazy
> to have to change their software to call bfq.weight the weight of a
> group. And are not willing to do it [1].
Then you need to educate them. Some of the issues were called out years
ago, at the time when we could have potentially renamed. A rename now
will solve nothing.
--
Jens Axboe
next prev parent reply other threads:[~2019-04-08 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 14:39 [PATCH 0/1] bfq: remove prefixes from cgroup filenames Paolo Valente
2019-04-08 14:39 ` [PATCH 1/1] block, bfq: delete "bfq" prefix " Paolo Valente
2019-04-08 14:49 ` Johannes Thumshirn
2019-04-08 14:54 ` Paolo Valente
2019-04-08 15:01 ` Jens Axboe
2019-04-08 15:04 ` Johannes Thumshirn
2019-04-08 15:05 ` Jens Axboe
2019-04-08 15:06 ` Paolo Valente
2019-04-08 15:11 ` Jens Axboe
2019-04-08 15:15 ` Paolo Valente
2019-04-08 15:08 ` Johannes Thumshirn
2019-04-08 15:13 ` Jens Axboe
2019-04-08 15:19 ` Paolo Valente
2019-04-08 15:14 ` Paolo Valente
2019-04-08 15:17 ` Jens Axboe [this message]
2019-04-08 17:01 ` Paolo Valente
2019-04-10 11:42 ` Ulf Hansson
2019-09-09 7:31 [PATCH 0/1] block, bfq: remove bfq prefix from cgroups filenames Paolo Valente
2019-09-09 7:31 ` [PATCH 1/1] block, bfq: delete "bfq" prefix from cgroup filenames Paolo Valente
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=ef1481e8-c664-5f17-4a19-bb90daabc0b7@kernel.dk \
--to=axboe@kernel.dk \
--cc=angeloruocco90@gmail.com \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=jthumshirn@suse.de \
--cc=lennart@poettering.net \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.cz \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.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).