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]
Message-ID: <20160809134110.GA28161@kroah.com>
Date:	Tue, 9 Aug 2016 15:41:10 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Bhaktipriya Shridhar <bhaktipriya96@...il.com>
Cc:	Julia Lawall <Julia.Lawall@...6.fr>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>
Subject: Re: [RFC] whci: Remove deprecated create_singlethread_workqueue

On Wed, Jul 27, 2016 at 02:39:16PM +0530, Bhaktipriya Shridhar wrote:
> alloc_ordered_workqueue replaces the deprecated
> create_singlethread_workqueue.
> 
> The workqueue "workqueue" has multiple workitems which may require
> ordering. Hence, a dedicated ordered workqueue has been used.
> Since the workqueue is not being used on a memory reclaim path,
> WQ_MEM_RECLAIM has not been set.
> 
> Can the workitems run concurrently? Is the ordering among work items necessary?

I don't know, sorry.  Almost no one has this hardware, so just fix it
the best you can and let's see what happens :)

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ