From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yishai Hadas Subject: Re: memory region limit at 32 GB? Date: Tue, 07 Aug 2012 11:18:05 +0300 Message-ID: <5020CF3D.8070205@dev.mellanox.co.il> References: <501FE7E9.20606@dev.mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Or Gerlitz , Albert Strasheim Cc: Roland Dreier , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On 8/7/2012 10:37 AM, Or Gerlitz wrote: > On Mon, Aug 6, 2012 at 6:51 PM, Yishai Hadas wrote: >> In the meanwhile I have found the root cause of the limit of log_num_mtt of 28. Plan to >> send in coming days an extra patch that enables value of 31 which match to 8TB. > nice doing. Just an ordering comment, for the upstream inclusion, it > seems that what we need is two patches > > 1. fix for some issues e.g around ints/longs and friends which is > likely to be the source of the bug which once fixed eliminated the > crashes you hit in the 28-30/31 range > > 2. the vmalloc etc patch you posted here > > This way you avoid reverting some code from patch #2 in patch #1 - it > helps with maintainance > > Or. I prefer that first patch will hold the limit of 28 as part of - otherwise system with large memory may fail to load,and the vmalloc fix won't help. Second patch fixes the limit and enables mapping of 8TB. Second patch was already sent. Yishai -- 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