linux-kernel - Re: workqueue thing

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: <1261387377.4314.37.camel@laptop>
Date:	Mon, 21 Dec 2009 10:22:57 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	torvalds@...ux-foundation.org, awalls@...ix.net,
	linux-kernel@...r.kernel.org, jeff@...zik.org, mingo@...e.hu,
	akpm@...ux-foundation.org, jens.axboe@...cle.com,
	rusty@...tcorp.com.au, cl@...ux-foundation.org,
	dhowells@...hat.com, arjan@...ux.intel.com, avi@...hat.com,
	johannes@...solutions.net, andi@...stfloor.org
Subject: Re: workqueue thing

On Mon, 2009-12-21 at 12:04 +0900, Tejun Heo wrote:
> When IO goes wrong, in extreme
> cases, it can easily take over thirty secs to recover and that's
> required by the hardware specifications, so anything which ends up
> waiting on IO can take a pretty long time.  The only piece of code
> which is necessary to support that is the code necessary to migrate
> back tasks to CPUs when they come online again.  It's not a lot of
> ugly code. 

Why does it need to get migrated back, there are no affinity promises if
you allow hotplug to continue, so it might as well complete and continue
on the other cpu.

And yes, it is a lot of very ugly code.

--
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/