linux-kernel - Re: [PATCH] kernel:async function call:introduce async_run

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090517140358.751e12b7@infradead.org>
Date:	Sun, 17 May 2009 14:03:58 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Cornelia Huck <cornelia.huck@...ibm.com>, tom.leiming@...il.com,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH] kernel:async function call:introduce
 async_run_inatomic(v2)

On Thu, 14 May 2009 05:19:39 +0200
Frederic Weisbecker <fweisbec@...il.com> wrote:

> But I wonder if async_run_inatomic() is really matching any common
> pattern inside the kernel.
> It seems to me rare to never need waiting for an async job completion.

there are some very good reasons to have the option to wait for all;
module unloading comes to mind for example.

I'd not like it to automatically punt all async "inatomic" work to a
separate space; that should be an option for the caller.
If the work is not going to take long, it's actually GOOD that you can
globally synchronize for it...

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