linux-kernel - Re: [PATCH] kthread: export park/unpark facility

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: <alpine.DEB.2.11.1507091848150.5134@nanos>
Date:	Thu, 9 Jul 2015 18:49:21 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jean Tourrilhes <jt@....hp.com>
cc:	Rusty Russell <rusty@...tcorp.com.au>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kthread: export park/unpark facility

On Thu, 9 Jul 2015, Jean Tourrilhes wrote:
> On Thu, Jul 09, 2015 at 10:05:02AM +0200, Thomas Gleixner wrote:
> > 
> > >  This patch should definitely help most modules.
> > 
> > And how exactly would this help modules?
> 
> 	Putting kthread to sleep and waking them up later is slightly
> tricky :
> 		http://www.linuxjournal.com/article/8144
> 
> 	The park and unpark API encapsulate this functionality in
> a pretty nice and clean API, and avoid duplicating this code in
> various modules. I'm all for sharing the joy ;-)

If you can come up with a proper use case, i.e. patch for a module,
then we can certainly talk about the exports. But without a user it
does not make any sense.

Thanks,

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