linux-kernel - Re: [PATCH 6/7] drm: use workqueue instead of slow-work

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]

Date:	Thu, 22 Jul 2010 23:17:36 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Dave Airlie <airlied@...hat.com>
CC:	sfrench@...ba.org, linux-kernel@...r.kernel.org,
	dri-devel@...ts.freedesktop.org, dhowells@...hat.com,
	anton@...ba.org, swhiteho@...hat.com
Subject: Re: [PATCH 6/7] drm: use workqueue instead of slow-work

On 07/22/2010 11:11 PM, Dave Airlie wrote:
> On Thu, 2010-07-22 at 22:45 +0200, Tejun Heo wrote:
>> On 07/20/2010 10:35 PM, Tejun Heo wrote:
>>> Workqueue can now handle high concurrency.  Convert drm_crtc_helper to
>>> use system_nrt_wq instead of slow-work.  The conversion is mostly
>>> straight forward.  One difference is that drm_helper_hpd_irq_event()
>>> no longer blocks and can be called from any context.
>>>
>>> Signed-off-by: Tejun Heo <tj@...nel.org>
>>> Cc: David Airlie <airlied@...ux.ie>
>>
>> David, can you please review the change?
> 
> Yes seems fine to me, in as much as I understand the difference between
> slow-work and workqueue, but if you say one replaces the other correctly
> now I'm happy for you to carry this patch.
> 
> Acked-by: Dave Airlie <airlied@...ux.ie>

Thank you.  Will push out to #for-next.

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