linux-kernel - Re: [PATCH RFC 09/22] block, cfq: replace CFQ with the BFQ-v0 I/O scheduler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160217111338.205bcaeb@lwn.net>
Date:	Wed, 17 Feb 2016 11:13:38 -0700
From:	Jonathan Corbet <corbet@....net>
To:	Tejun Heo <tj@...nel.org>
Cc:	Mark Brown <broonie@...nel.org>,
	Paolo Valente <paolo.valente@...aro.org>,
	Jens Axboe <axboe@...nel.dk>,
	Fabio Checconi <fchecconi@...il.com>,
	Arianna Avanzini <avanzini.arianna@...il.com>,
	linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
	ulf.hansson@...aro.org, linus.walleij@...aro.org
Subject: Re: [PATCH RFC 09/22] block, cfq: replace CFQ with the BFQ-v0 I/O
 scheduler

On Wed, 17 Feb 2016 12:04:29 -0500
Tejun Heo <tj@...nel.org> wrote:

> idk, istr this coming up some months ago and there really weren't good
> arguments for furthering out-of-line generated docs.  I'm sure there
> are people building and checking for errors but that doesn't indicate
> the actual usefulness or that we shouldn't move away from it.

This might come as a real surprise to the subsystems that are putting a
lot of work into said docs.  *You* might not find them useful but, for
example, the DRM folks have told me that they credit better docs with an
increase in the quality of the code submissions they are getting.  Much
of that work is inline, but in the code is not always the best place for
everything.

There's a set of us working to improve the generation system, making it
so that even ordinary kernel developers can manage to get it to work.
Sorry if you don't this stuff useful, but I hope you'll not mind if
others keep the documentation in good form?

In the case that started this discussion, it's the out-of-line generation
that raises the alarm when things do go out of sync, helping to keep the
docs current.  

jon