Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936116Ab3DQP0a (ORCPT ); Wed, 17 Apr 2013 11:26:30 -0400 Received: from www.sr71.net ([198.145.64.142]:41734 "EHLO blackbird.sr71.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933146Ab3DQP03 (ORCPT ); Wed, 17 Apr 2013 11:26:29 -0400 Message-ID: <516EBF23.2090600@sr71.net> Date: Wed, 17 Apr 2013 08:26:27 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Darren Hart CC: zhang.yi20@zte.com.cn, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Ingo Molnar , Peter Zijlstra , Thomas Gleixner , Dave Hansen Subject: Re: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage References: <516EAF31.8000107@linux.intel.com> In-Reply-To: <516EAF31.8000107@linux.intel.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1370 Lines: 30 On 04/17/2013 07:18 AM, Darren Hart wrote: >>> This also needs a comment in futex.h describing the usage of the offset >>> field in union futex_key as well as above get_futex_key describing the >>> key for shared mappings. >>> >> As far as I know , the max size of one hugepage is 1 GBytes for x86 cpu. >> Can some other cpus support greater hugepage even more than 4 GBytes? If >> so, we can change the type of 'offset' from int to long to avoid >> truncating. > > I discussed this with Dave Hansen, on CC, and he thought we needed 9 > bits, so even on x86 32b we should be covered. I think the problem is actually on 64-bit since you still only have 32-bits in an 'int' there. I guess it's remotely possible that we could have some mega-super-huge-gigantic pages show up in hardware some day, or that somebody would come up with software-only one. I bet there's a lot more code that will break in the kernel than this futex code, though. The other option would be to start #defining some build-time constant for what the largest possible huge page size is, then BUILD_BUG_ON() it. Or you can just make it a long ;) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/