On 06/10/2016 12:38 PM, Johannes Thumshirn wrote:
…
>
> Tested in a Boot from FCoE scenario using a BCM57840.
This got merged over the weekend. Thanks for that. I will try to look
into the other two (bnx2i, bnx2fc) and convert them as well within this
week.
Sebastian
--
To unsubscribe from this
On Tue, Apr 12, 2016 at 05:16:54PM +0200, 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 th
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 m
; r...@linutronix.de, fcoe-de...@open-fcoe.org, "Chad
> Dupuis"
> Sent: Thursday, June 9, 2016 9:09:37 AM
> Subject: Re: [PREEMPT-RT] [PATCH v2] scsi/fcoe: convert to kworker
>
> On 04/22/2016 06:39 PM, Laurence Oberman wrote:
> > I have fcoe for testing.
>
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 "unsubs
Hellwig"
Cc: linux-scsi@vger.kernel.org, "Martin K. Petersen"
, "Vasu Dev" ,
r...@linutronix.de, fcoe-de...@open-fcoe.org, "Chad Dupuis"
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:2
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 kth
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 p
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 per-CPU
thread. By using the kworker infrastructure this is no longe
9 matches
Mail list logo
