summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorKa-Cheong Poon <ka-cheong.poon@oracle.com>2019-10-02 21:11:08 -0700
committerDavid S. Miller <davem@davemloft.net>2019-10-03 12:11:08 -0700
commit9b17f5884be4484e4d9090a9dccf17e763e0589b (patch)
treec82ada52740a8a0c38cc6931ef83ddd742b120f2 /scripts
parentdf1025fc279c22f9bdd319a6c38c52cc3f4b7c64 (diff)
downloadlinux-9b17f5884be4484e4d9090a9dccf17e763e0589b.tar.gz
linux-9b17f5884be4484e4d9090a9dccf17e763e0589b.tar.bz2
linux-9b17f5884be4484e4d9090a9dccf17e763e0589b.zip
net/rds: Use DMA memory pool allocation for rds_header
Currently, RDS calls ib_dma_alloc_coherent() to allocate a large piece of contiguous DMA coherent memory to store struct rds_header for sending/receiving packets. The memory allocated is then partitioned into struct rds_header. This is not necessary and can be costly at times when memory is fragmented. Instead, RDS should use the DMA memory pool interface to handle this. The DMA addresses of the pre- allocated headers are stored in an array. At send/receive ring initialization and refill time, this arrary is de-referenced to get the DMA addresses. This array is not accessed at send/receive packet processing. Suggested-by: HÃ¥kon Bugge <haakon.bugge@oracle.com> Signed-off-by: Ka-Cheong Poon <ka-cheong.poon@oracle.com> Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions