From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752188AbZHXKWI (ORCPT ); Mon, 24 Aug 2009 06:22:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751856AbZHXKWH (ORCPT ); Mon, 24 Aug 2009 06:22:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:14973 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750933AbZHXKWG (ORCPT ); Mon, 24 Aug 2009 06:22:06 -0400 Message-ID: <4A926A0A.1000607@redhat.com> Date: Mon, 24 Aug 2009 18:23:06 +0800 From: Amerigo Wang User-Agent: Thunderbird 2.0.0.22 (X11/20090719) MIME-Version: 1.0 To: Bernhard Walle CC: Ingo Molnar , Andrew Morton , linux-kernel@vger.kernel.org, tony.luck@intel.com, linux-ia64@vger.kernel.org, nhorman@redhat.com, ebiederm@xmission.com, andi@firstfloor.org, fenghua.yu@intel.com, kamezawa.hiroyu@jp.fujitsu.com, avorontsov@ru.mvista.com Subject: Re: [Patch 5/8] ia64: implement crashkernel=auto References: <20090821065637.4855.32234.sendpatchset@localhost.localdomain> <20090821065729.4855.47860.sendpatchset@localhost.localdomain> <20090821172407.d3a5cd2b.akpm@linux-foundation.org> <20090822111816.GA12281@elte.hu> <4A91F57D.10708@redhat.com> <20090824074318.GB2424@elte.hu> <20090824082148.GA16457@mail1.bwalle.de> In-Reply-To: <20090824082148.GA16457@mail1.bwalle.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Bernhard Walle wrote: > * Ingo Molnar [2009-08-24 09:43]: > >> * Amerigo Wang wrote: >> >>> The reason that I kept 2ULL<<30 instead of 1ULL<<31 is that '1<<30' is >>> exactly 1G, so 2ULL<<30 can be easily read as 2G. ;) >>> >> i have no trouble reading 1ULL<<31 as 2G ;-) OTOH, the logic and >> pattern of the comparisons (especially without the comment) looked >> odd at first sight, until i noticed this. >> > > Why not just something like > > #define KBYTE(x) ((x)*1024ULL) > #define MBYTE(x) ((x)*1024ULL*1024) > #define GBYTE(x) ((x)*1024ULL*1024*1024) > #define TBYTE(x) ((x)*1024ULL*1024*1024*1024) > > I find GBYTE(2) much easier to read than 1ULL<<31. Honestly, I would > add a comment '/* 2G */' if I would write 1ULL<<31 in own code. > > But I'm of course not one of that super kernel hackers. ;-) > > Yeah, great. Here we only need MBYTES() and GBYTES(). ;) Thanks.