On 07/10/2017 09:06 AM, Yijing Wang wrote:
> Now libsas hotplug work is static, every sas event type has its own
> static work, LLDD driver queue the hotplug work into shost->work_q.
> If LLDD driver burst post lots hotplug events to libsas, the hotplug
> events may pending in the workqueue like
>
On 07/10/2017 09:06 AM, Yijing Wang wrote:
> Now libsas hotplug work is static, every sas event type has its own
> static work, LLDD driver queue the hotplug work into shost->work_q.
> If LLDD driver burst post lots hotplug events to libsas, the hotplug
> events may pending in the workqueue like
>
There is no special meaning for the pool size, if flutter of > 25 events,
notify sas events will return error, and the further step work is
depending on LLDD drivers.
I hope libsas could do more work in this case, but now it seems a little
difficult, this patch may be a
There is no special meaning for the pool size, if flutter of > 25 events,
notify sas events will return error, and the further step work is
depending on LLDD drivers.
I hope libsas could do more work in this case, but now it seems a little
difficult, this patch may be a
On 12/07/2017 09:47, wangyijing wrote:
在 2017/7/12 16:17, John Garry 写道:
On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event
On 12/07/2017 09:47, wangyijing wrote:
在 2017/7/12 16:17, John Garry 写道:
On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event
在 2017/7/12 16:17, John Garry 写道:
> On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_POOL_SIZE];
在 2017/7/12 16:17, John Garry 写道:
> On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_POOL_SIZE];
On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_POOL_SIZE];
int error;
Hi Yijing,
So now we are creating a static
On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_POOL_SIZE];
int error;
Hi Yijing,
So now we are creating a static
>> -unsigned long port_events_pending;
>> -unsigned long phy_events_pending;
>> +struct asd_sas_event port_events[PORT_POOL_SIZE];
>> +struct asd_sas_event phy_events[PHY_POOL_SIZE];
>>
>> int error;
>
> Hi Yijing,
>
> So now we are creating a static pool of events per
>> -unsigned long port_events_pending;
>> -unsigned long phy_events_pending;
>> +struct asd_sas_event port_events[PORT_POOL_SIZE];
>> +struct asd_sas_event phy_events[PHY_POOL_SIZE];
>>
>> int error;
>
> Hi Yijing,
>
> So now we are creating a static pool of events per
On 10/07/2017 08:06, Yijing Wang wrote:
Now libsas hotplug work is static, every sas event type has its own
static work, LLDD driver queue the hotplug work into shost->work_q.
If LLDD driver burst post lots hotplug events to libsas, the hotplug
events may pending in the workqueue like
On 10/07/2017 08:06, Yijing Wang wrote:
Now libsas hotplug work is static, every sas event type has its own
static work, LLDD driver queue the hotplug work into shost->work_q.
If LLDD driver burst post lots hotplug events to libsas, the hotplug
events may pending in the workqueue like
Now libsas hotplug work is static, every sas event type has its own
static work, LLDD driver queue the hotplug work into shost->work_q.
If LLDD driver burst post lots hotplug events to libsas, the hotplug
events may pending in the workqueue like
shost->work_q
new work[PORTE_BYTES_DMAED] -->
Now libsas hotplug work is static, every sas event type has its own
static work, LLDD driver queue the hotplug work into shost->work_q.
If LLDD driver burst post lots hotplug events to libsas, the hotplug
events may pending in the workqueue like
shost->work_q
new work[PORTE_BYTES_DMAED] -->
16 matches
Mail list logo