From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>, Tejun Heo <tj@kernel.org>
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>,
noreply-spamdigest via bfq-iosched <bfq-iosched@googlegroups.com>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
cgroups@vger.kernel.org
Subject: Re: [PATCH 0/1] block, bfq: remove bfq prefix from cgroups filenames
Date: Mon, 16 Sep 2019 10:01:40 -0600 [thread overview]
Message-ID: <91deff5b-4a0d-a7ef-8bb2-7e7e5dad767b@kernel.dk> (raw)
In-Reply-To: <64329DDB-FFF4-4709-83B1-39D5E6BF6AB6@linaro.org>
On 9/16/19 9:21 AM, Paolo Valente wrote:
>
>
>> Il giorno 16 set 2019, alle ore 17:16, Tejun Heo <tj@kernel.org> ha scritto:
>>
>> Hello, Paolo.
>>
>> On Mon, Sep 16, 2019 at 05:07:29PM +0200, Paolo Valente wrote:
>>> Tejun, could you put your switch-off-io-cost code into a standalone
>>> patch, so that I can put it together with this one in a complete
>>> series?
>>
>> It was more of a proof-of-concept / example, so the note in the email
>> that the code is free to be modified / used any way you see fit. That
>> said, if you like it as it is, I can surely prep it as a standalone
>> patch.
>>
>
> AFAICT your proposal contains no evident error. Plus, no one seems to
> have complained about the idea (regardless from the exact
> implementation). So I guess the best next step is to go for it.
Not filling me with a lot of confidence that you actually tested it?
--
Jens Axboe
next prev parent reply other threads:[~2019-09-16 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2019-09-16 14:56 ` [PATCH 0/1] block, bfq: remove bfq prefix from cgroups filenames Paolo Valente
2019-09-16 15:01 ` Jens Axboe
2019-09-16 15:07 ` Paolo Valente
2019-09-16 15:16 ` Tejun Heo
2019-09-16 15:21 ` Paolo Valente
2019-09-16 16:01 ` Jens Axboe [this message]
2019-09-16 16:45 ` Paolo Valente
2019-09-17 15:14 ` Tejun Heo
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=91deff5b-4a0d-a7ef-8bb2-7e7e5dad767b@kernel.dk \
--to=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=cgroups@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.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 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.