linux-kernel - Re: [PATCH] async: Manage execution domains

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100307141150.51b3518a@linux.intel.com>
Date:	Sun, 7 Mar 2010 14:11:50 -0800
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	linux-kernel@...r.kernel.org,
	Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: [PATCH] async: Manage execution domains

On Sun,  7 Mar 2010 19:12:29 +0000
Chris Wilson <chris@...is-wilson.co.uk> wrote:

> Currently execution domains do not interact well with full
> synchronisation requests. If the sync request is performed before the
> async task has begun, then the manager will never schedule() and so
> busy-wait forever on a UP box. By reorganising the tasks into both a
> per-domain and global list, we can either wait on a single execution
> domain or globally over all tasks, as intended.

the intention has never been to wait for all tasks, at least not for
tasks that have their own domain rather than using the global domain.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/