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] [day] [month] [year] [list]
Date:	Thu, 23 Aug 2012 20:26:30 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Lauro Ramos Venancio <lauro.venancio@...nbossa.org>,
	Aloisio Almeida Jr <aloisio.almeida@...nbossa.org>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nfc: use system_nrt_wq instead of custom ones

Hi Tejun,

On Wed, Aug 22, 2012 at 04:22:16PM -0700, Tejun Heo wrote:
> NFC is using a number of custom ordered workqueues w/ WQ_MEM_RECLAIM.
> WQ_MEM_RECLAIM is unnecessary unless NFC is gonna be used as transport
> for storage device, and all use cases match one work item to one
> ordered workqueue - IOW, there's no actual ordering going on at all
> and using system_nrt_wq gives the same behavior.
> 
> There's nothing to be gained by using custom workqueues.  Use
> system_nrt_wq instead and drop all the custom ones.
> 
> Only compile tested.
Tested here, and it works fine.
I'm queueing this one up to my nfc-next branch, thanks a lot for the follow
up.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ