linux-kernel - Re: [PATCH 17/20] [SCSI] mpt3sas: Use alloc_ordered_workqueue() API instead of create_singlethread

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: <557B4923.1020608@stratus.com>
Date:	Fri, 12 Jun 2015 17:03:31 -0400
From:	Joe Lawrence <joe.lawrence@...atus.com>
To:	Sreekanth Reddy <sreekanth.reddy@...gotech.com>, <jejb@...nel.org>,
	<hch@...radead.org>
CC:	<martin.petersen@...cle.com>, <linux-scsi@...r.kernel.org>,
	<JBottomley@...allels.com>, <Sathya.Prakash@...gotech.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 17/20] [SCSI] mpt3sas: Use alloc_ordered_workqueue() API
 instead of create_singlethread_workqueue() API

On 06/12/2015 05:42 AM, Sreekanth Reddy wrote:
...
> +#if defined(alloc_ordered_workqueue)
> +	ioc->firmware_event_thread = alloc_ordered_workqueue(
> +		ioc->firmware_event_name, WQ_MEM_RECLAIM);
> +#else
> +		ioc->firmware_event_thread = create_singlethread_workqueue(
>  	    ioc->firmware_event_name);
> +#endif

Hi Sreekanth,

I think the upstream version of this code can safely assume
alloc_ordered_workqueue is defined, no?

Regards,

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