Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker

2016-06-09 Thread Sebastian Andrzej Siewior
On 06/09/2016 03:15 PM, Laurence Oberman wrote: > Hello Hi, > Apologies, somehow this fell off my radar. > I will get the FCOE test bed up and get it done ASAP. Thanks > > Regards > Laurence Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a

Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker

2016-06-09 Thread Laurence Oberman
t;h...@infradead.org>, linux-scsi@vger.kernel.org, > "Martin K. Petersen" > <martin.peter...@oracle.com>, "Vasu Dev" <vasu@intel.com>, > r...@linutronix.de, fcoe-de...@open-fcoe.org, "Chad > Dupuis" <chad.dup...@qlogic.com> > Sent: Thursday,

Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker

2016-06-09 Thread Sebastian Andrzej Siewior
On 04/22/2016 06:39 PM, Laurence Oberman wrote: > I have fcoe for testing. > I will pull this in next week and test it. any update? > > Laurence Oberman > Principal Software Maintenance Engineer > Red Hat Global Support Services Sebastian -- To unsubscribe from this list: send the line

Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker

2016-04-22 Thread Laurence Oberman
upuis" <chad.dup...@qlogic.com> Sent: Friday, April 22, 2016 11:49:45 AM Subject: Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker On Fri, 2016-04-22 at 17:27 +0200, Sebastian Andrzej Siewior wrote: > On 04/12/2016 05:16 PM, Sebastian Andrzej Siewior wrote: > > The driver c

Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker

2016-04-22 Thread James Bottomley
On Fri, 2016-04-22 at 17:27 +0200, Sebastian Andrzej Siewior wrote: > On 04/12/2016 05:16 PM, Sebastian Andrzej Siewior wrote: > > The driver creates its own per-CPU threads which are updated based > > on > > CPU hotplug events. It is also possible to use kworkers and remove > > some > > of the

Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker

2016-04-22 Thread Sebastian Andrzej Siewior
On 04/12/2016 05:16 PM, Sebastian Andrzej Siewior wrote: > The driver creates its own per-CPU threads which are updated based on > CPU hotplug events. It is also possible to use kworkers and remove some > of the kthread infrastrucure. > > The code checked ->thread to decide if there is an active