[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1488848033.3125.12.camel@sandisk.com>
Date: Tue, 7 Mar 2017 00:54:06 +0000
From: Bart Van Assche <Bart.VanAssche@...disk.com>
To: "tj@...nel.org" <tj@...nel.org>,
"paolo.valente@...aro.org" <paolo.valente@...aro.org>,
"axboe@...nel.dk" <axboe@...nel.dk>
CC: "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"fchecconi@...il.com" <fchecconi@...il.com>,
"avanzini.arianna@...il.com" <avanzini.arianna@...il.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"broonie@...nel.org" <broonie@...nel.org>
Subject: Re: [PATCH RFC 13/14] block, bfq: boost the throughput with random
I/O on NCQ-capable HDDs
On Sat, 2017-03-04 at 17:01 +0100, Paolo Valente wrote:
> @@ -8301,7 +8297,7 @@ static struct blkcg_policy blkcg_policy_bfq = {
> static int __init bfq_init(void)
> {
> int ret;
> - char msg[50] = "BFQ I/O-scheduler: v6";
> + char msg[50] = "BFQ I/O-scheduler: v7r3";
>
> #ifdef CONFIG_BFQ_GROUP_IOSCHED
> ret = blkcg_policy_register(&blkcg_policy_bfq);
In the Linux kernel the kernel as a whole has a version number but we
do not assign a version number to individual core components.
Bart.
Powered by blists - more mailing lists