linux-kernel - Re: [PATCHSET] workqueue: concurrency managed workqueue, take#5

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]

Date:	Tue, 15 Jun 2010 00:43:17 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	mingo@...e.hu, awalls@...ix.net, linux-kernel@...r.kernel.org,
	jeff@...zik.org, rusty@...tcorp.com.au, cl@...ux-foundation.org,
	dhowells@...hat.com, arjan@...ux.intel.com,
	johannes@...solutions.net, oleg@...hat.com, axboe@...nel.dk
Subject: Re: [PATCHSET] workqueue: concurrency managed workqueue, take#5

Hello,

On 06/15/2010 12:35 AM, Andrew Morton wrote:
> Nobody's going to remember all that stuff except yourself, and the info
> might be out of date.  So please update and maintain that information
> and retain it with the patchset.
> 
> eg: "<NEED SOME BACKING NUMBERS>".  And "Please read the patch
> description of the last patch for more details" is out of date.
> 
> Because right now I have a bunch of code in my inbox and little
> (actually "no") idea why anyone might want to merge it into anything.
>
> Trying to review a large patchset when you don't have an overall
> picture of what it's trying to do and how it's trying to do it is
> rather painful - you have to work all that stuff out from the
> implementation.  It's also error-prone if the implementation doesn't
> implement that which the author thinks it implements (ie: if it has
> design bugs).

Well, basics of the whole thing didn't change all that much since the
first take and most people on cc list were cc'd on each take.  The
biggest reason I'm still carrying the whole patchset is due to the
scheduler changes.  The numbers are in the third take (which you can
follow the links to find out).  Anyways, I'll write up another summary
tomorrow.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/