From: Paolo Valente <paolo.valente@linaro.org> To: Bart Van Assche <bart.vanassche@sandisk.com> Cc: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>, Fabio Checconi <fchecconi@gmail.com>, Arianna Avanzini <avanzini.arianna@gmail.com>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>, "linus.walleij@linaro.org" <linus.walleij@linaro.org>, "broonie@kernel.org" <broonie@kernel.org> Subject: Re: [PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq Date: Tue, 14 Mar 2017 15:12:06 +0100 [thread overview] Message-ID: <3498DE72-65D0-4D1A-9CA6-9176137AF6CE@linaro.org> (raw) In-Reply-To: <1D08B61A9CF0974AA09887BE32D889DA0DA827@ULS-OP-MBXIP03.sdcorp.global.sandisk.com> > Il giorno 07 mar 2017, alle ore 01:22, Bart Van Assche = <bart.vanassche@sandisk.com> ha scritto: >=20 > On 03/04/2017 08:01 AM, Paolo Valente wrote: >> Some patch generates WARNINGS with checkpatch.pl, but these WARNINGS >> seem to be either unavoidable for the involved pieces of code (which >> the patch just extends), or false positives. >=20 > The code in this series looks reasonably clean from a code style point > of view, Great, thanks! > but please address all checkpatch warnings that can be > addressed easily. A few examples of such checkpatch warnings: >=20 > ERROR: "foo * bar" should be "foo *bar" >=20 The offending line is: *(__PTR) =3D (u64)__data * NSEC_PER_USEC; so this seems a false positive. > WARNING: Symbolic permissions 'S_IRUGO|S_IWUSR' are not preferred. > Consider using octal permissions '0644'. >=20 I have used symbolic permissions because I find them much easier to remember and decode than numeric constants, and because it is done so in cfq-iosched.c, deadline-iosched.c and now mq-deadline.c. But, since you share this checkpatch complain, I will switch to constants. Thanks, Paolo > Thanks, >=20 > Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Valente <paolo.valente@linaro.org> To: Bart Van Assche <bart.vanassche@sandisk.com> Cc: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>, Fabio Checconi <fchecconi@gmail.com>, Arianna Avanzini <avanzini.arianna@gmail.com>, "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>, "linus.walleij@linaro.org" <linus.walleij@linaro.org>, "broonie@kernel.org" <broonie@kernel.org> Subject: Re: [PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq Date: Tue, 14 Mar 2017 15:12:06 +0100 [thread overview] Message-ID: <3498DE72-65D0-4D1A-9CA6-9176137AF6CE@linaro.org> (raw) In-Reply-To: <1D08B61A9CF0974AA09887BE32D889DA0DA827@ULS-OP-MBXIP03.sdcorp.global.sandisk.com> > Il giorno 07 mar 2017, alle ore 01:22, Bart Van Assche <bart.vanassche@sandisk.com> ha scritto: > > On 03/04/2017 08:01 AM, Paolo Valente wrote: >> Some patch generates WARNINGS with checkpatch.pl, but these WARNINGS >> seem to be either unavoidable for the involved pieces of code (which >> the patch just extends), or false positives. > > The code in this series looks reasonably clean from a code style point > of view, Great, thanks! > but please address all checkpatch warnings that can be > addressed easily. A few examples of such checkpatch warnings: > > ERROR: "foo * bar" should be "foo *bar" > The offending line is: *(__PTR) = (u64)__data * NSEC_PER_USEC; so this seems a false positive. > WARNING: Symbolic permissions 'S_IRUGO|S_IWUSR' are not preferred. > Consider using octal permissions '0644'. > I have used symbolic permissions because I find them much easier to remember and decode than numeric constants, and because it is done so in cfq-iosched.c, deadline-iosched.c and now mq-deadline.c. But, since you share this checkpatch complain, I will switch to constants. Thanks, Paolo > Thanks, > > Bart.
next prev parent reply other threads:[~2017-03-14 14:12 UTC|newest] Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-04 16:01 [PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 01/14] block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler Paolo Valente 2017-03-05 15:16 ` Jens Axboe 2017-03-05 16:02 ` Paolo Valente 2017-03-05 16:02 ` Paolo Valente 2017-03-06 20:46 ` Jens Axboe 2017-03-14 11:28 ` Paolo Valente 2017-03-14 11:28 ` Paolo Valente 2017-03-06 19:40 ` Bart Van Assche 2017-03-06 19:40 ` Bart Van Assche 2017-03-14 14:18 ` Paolo Valente 2017-03-14 14:18 ` Paolo Valente 2017-03-18 12:08 ` Paolo Valente 2017-03-18 12:08 ` Paolo Valente 2017-03-18 15:24 ` Bart Van Assche 2017-03-18 15:24 ` Bart Van Assche 2017-03-19 11:45 ` Paolo Valente 2017-03-19 11:45 ` Paolo Valente 2017-03-07 23:22 ` Jens Axboe 2017-03-18 12:41 ` Paolo Valente 2017-03-18 12:41 ` Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 02/14] block, bfq: add full hierarchical scheduling and cgroups support Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 03/14] block, bfq: improve throughput boosting Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 04/14] block, bfq: modify the peak-rate estimator Paolo Valente 2017-03-07 0:47 ` Bart Van Assche 2017-03-07 0:47 ` Bart Van Assche 2017-03-04 16:01 ` [PATCH RFC 05/14] block, bfq: add more fairness with writes and slow processes Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 06/14] block, bfq: improve responsiveness Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 07/14] block, bfq: reduce I/O latency for soft real-time applications Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 08/14] block, bfq: preserve a low latency also with NCQ-capable drives Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 09/14] block, bfq: reduce latency during request-pool saturation Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 10/14] block, bfq: add Early Queue Merge (EQM) Paolo Valente 2017-03-07 17:44 ` Jens Axboe 2017-03-15 12:01 ` Paolo Valente 2017-03-15 12:01 ` Paolo Valente 2017-03-15 15:47 ` Jens Axboe 2017-03-15 16:30 ` Jens Axboe 2017-03-15 16:59 ` Paolo Valente 2017-03-15 16:59 ` Paolo Valente 2017-03-15 21:00 ` Jens Axboe 2017-03-18 10:33 ` Paolo Valente 2017-03-18 10:33 ` Paolo Valente 2017-03-15 16:56 ` Jens Axboe 2017-03-15 17:02 ` Paolo Valente 2017-03-15 17:02 ` Paolo Valente 2017-03-15 21:01 ` Jens Axboe 2017-03-04 16:01 ` [PATCH RFC 11/14] block, bfq: reduce idling only in symmetric scenarios Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 12/14] block, bfq: boost the throughput on NCQ-capable flash-based devices Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 13/14] block, bfq: boost the throughput with random I/O on NCQ-capable HDDs Paolo Valente 2017-03-07 0:54 ` Bart Van Assche 2017-03-07 0:54 ` Bart Van Assche 2017-03-14 14:12 ` Paolo Valente 2017-03-14 14:12 ` Paolo Valente 2017-03-04 16:01 ` [PATCH RFC 14/14] block, bfq: handle bursts of queue activations Paolo Valente 2017-03-06 7:43 ` [PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq Markus Trippelsdorf 2017-03-31 13:27 ` Paolo Valente 2017-03-31 13:27 ` Paolo Valente 2017-03-07 0:22 ` Bart Van Assche 2017-03-07 0:22 ` Bart Van Assche 2017-03-14 14:12 ` Paolo Valente [this message] 2017-03-14 14:12 ` Paolo Valente 2017-03-07 1:00 ` Bart Van Assche 2017-03-07 1:00 ` Bart Van Assche 2017-03-14 15:35 ` Paolo Valente 2017-03-14 15:35 ` Paolo Valente 2017-03-14 15:42 ` Jens Axboe 2017-03-14 16:32 ` Bart Van Assche 2017-03-14 16:32 ` Bart Van Assche 2017-03-18 10:52 ` Paolo Valente 2017-03-18 10:52 ` Paolo Valente 2017-03-18 17:09 ` Linus Walleij 2017-03-18 17:46 ` Bart Van Assche 2017-03-18 17:46 ` Bart Van Assche 2017-03-18 20:46 ` Linus Walleij 2017-03-19 12:14 ` Paolo Valente 2017-03-19 12:14 ` Paolo Valente 2017-03-20 18:40 ` Jens Axboe
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=3498DE72-65D0-4D1A-9CA6-9176137AF6CE@linaro.org \ --to=paolo.valente@linaro.org \ --cc=avanzini.arianna@gmail.com \ --cc=axboe@kernel.dk \ --cc=bart.vanassche@sandisk.com \ --cc=broonie@kernel.org \ --cc=fchecconi@gmail.com \ --cc=linus.walleij@linaro.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.