From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Van Assche Subject: Re: multipath IB/srp fail-over testing lands up in dump stack in swiotlb_alloc_coherent() Date: Sun, 12 Jun 2016 23:32:53 -0700 Message-ID: <2d316ddf-9a2a-3aba-cf2d-fcdaafbaa848@sandisk.com> References: <19156300.41876496.1465771227395.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19156300.41876496.1465771227395.JavaMail.zimbra-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Yishai Hadas Cc: Laurence Oberman , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-rdma@vger.kernel.org On 06/12/2016 03:40 PM, Laurence Oberman wrote: > Jun 8 10:12:52 jumpclient kernel: mlx5_core 0000:08:00.1: swiotlb buffer is full (sz: 266240 bytes) > Jun 8 10:12:52 jumpclient kernel: swiotlb: coherent allocation failed for device 0000:08:00.1 size=266240 Hello, I think the above means that the coherent memory allocation succeeded but that the test dev_addr + size - 1 <= DMA_BIT_MASK(32) failed. Can someone from Mellanox tell us whether or not it would be safe to set coherent_dma_mask to DMA_BIT_MASK(64) for the mlx4 and mlx5 drivers? Thanks, Bart. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html