On 26 July 2016 at 19:01, Bhaktipriya Shridhar wrote:
> The workqueue "workq" provides support for sd/mmc async request, which
> makes next request do dma_map_sg() while previous request transferring
> data.
>
> The workqueue has a single workitem(>work) and hence doesn't
On 26 July 2016 at 19:01, Bhaktipriya Shridhar wrote:
> The workqueue "workq" provides support for sd/mmc async request, which
> makes next request do dma_map_sg() while previous request transferring
> data.
>
> The workqueue has a single workitem(>work) and hence doesn't require
> ordering.
On Tue, Jul 26, 2016 at 10:31:06PM +0530, Bhaktipriya Shridhar wrote:
> The workqueue "workq" provides support for sd/mmc async request, which
> makes next request do dma_map_sg() while previous request transferring
> data.
>
> The workqueue has a single workitem(>work) and hence doesn't require
The workqueue "workq" provides support for sd/mmc async request, which
makes next request do dma_map_sg() while previous request transferring
data.
The workqueue has a single workitem(>work) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path. Hence,
the
On Tue, Jul 26, 2016 at 10:31:06PM +0530, Bhaktipriya Shridhar wrote:
> The workqueue "workq" provides support for sd/mmc async request, which
> makes next request do dma_map_sg() while previous request transferring
> data.
>
> The workqueue has a single workitem(>work) and hence doesn't require
The workqueue "workq" provides support for sd/mmc async request, which
makes next request do dma_map_sg() while previous request transferring
data.
The workqueue has a single workitem(>work) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path. Hence,
the
6 matches
Mail list logo