linux-kernel - Re: [RFC][PATCH 03/10] workqueue: It is likely that WORKER_NOT

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: <1292026337.5015.1542.camel@gandalf.stny.rr.com>
Date:	Fri, 10 Dec 2010 19:12:17 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC][PATCH 03/10] workqueue: It is likely that
 WORKER_NOT_RUNNING is true

On Sat, 2010-12-11 at 01:09 +0100, Tejun Heo wrote:
> On 12/11/2010 01:08 AM, Steven Rostedt wrote:
> > On Tue, 2010-12-07 at 10:49 +0100, Tejun Heo wrote:
> > 
> >> Yeah, I was lost thinking about the busiest case where workers are
> >> busy processing works consecutively.  Usually workers are of course
> >> switching in and out of idle state all the time.
> >>
> >> How about just dropping likely/unlikely?
> > 
> > OK, if I just remove it, can I add your Acked-by?
> 
> Sure, then, I'll route it through my tree.


OK, I'll post a new patch series again. Just pluck it from that, and let
me know so I can remove it from my tree.

Thanks,

-- Steve


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