On 17 April 2011 09:09, Lin Tony-B19295 <B19295@xxxxxxxxxxxxx> wrote: > Hi Per > > Just have a glance of your patch, good thinking. But I have a question about this patch. You modified mmc_test to test your driver. Does it mean your driver's performance enhancement depends on application? I added those tests in mmc_test to compare the performance between blocking and none blocking. Basically it tests performance gain if running dma_map and dma_unmap in parallel with the transfer, compared to running dma_map and dma_unmap in serial with the transfer. > The caller must have to know the next request so that could make driver prepare next during current transfer? mmc_test tests the ideal performance gain (all request are linked together). > So testing your driver with blocking request & non blocking request will have different throughput due to different application mechanism. Yes. I added support for mmc non blocking in the mmc block device but the performance gain here depends on how the FS-requests are propagated down to the mmc block device. If the request are added one by one, waiting for the last request to complete before adding the new request, there will be no performance gain. To test the mmc block performance I have run IOZone in user space. > Thanks > > BR > Tony BR Per -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
