Re: mlx4: using dma_sync_single_for_cpu/dma_sync_single_for_cpu for writing MTT instead of WRITE_MTT hcr command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 9 Jul 2014 18:40:46 +0530
Bob Biloxi <iambobbiloxi@xxxxxxxxx> wrote:

> Hi,
> 
> I was going through the mr.c file as part of understanding WRITE_MTT
> command in the mlx4 code.
> 
> I could see that instead of issuing the WRITE_MTT HCR command, in case
> of SRIOV, we're directly accessing the ICM space for the MTT Table,
> taking the ownership and updating it. We're doing this using
> dma_sync_single_for_cpu and dma_sync_single_for_cpu.
> 
> I was curious as to why this approach was chosen instead of using the
> HCR command.
> 
> Can anyone please explain the reason/motivation behind this approach?
>
Performance. Direct write to memory is much faster than via HCR

-Jack

> 
> 
> Thanks so much,
> 
> 
> Best Regards,
> Marc
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma"
> in the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux