Date: Tue, 7 Apr 2009 22:31:48 +1000
From: Nick Andrew <nick@nick-andrew.net>
To: don fisher <hdf3@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH try #1] Kconfig: cleanup block/Kconfig help descriptions
Message-ID: <20090407123148.GA11750@mail.local.tull.net>
References: <20080223225640.20233.12405.stgit@marcab.local.tull.net> <49BDC438.6080900@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49BDC438.6080900@comcast.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 905
Lines: 30

On Sun, Mar 15, 2009 at 08:15:04PM -0700, don fisher wrote:
> Nick,
>
> I am trying to configure a linux-2.6.28.7 kernel.
>
> Please explain why the switch for large block devices should be !64BIT.  
> I have a 64BIT system and currently cannot generate files greater than  
> 2TB. Is this the problem? Should this be true for 64BIT systems?

Sorry I didn't see this email earlier.

Probably due to this:

#ifdef CONFIG_LBD
typedef u64 sector_t;
typedef u64 blkcnt_t;
#else
typedef unsigned long sector_t;
typedef unsigned long blkcnt_t;
#endif

With a 64-bit machine, your sector_t and blkcnt_t are already 64 bits
wide, so CONFIG_LBD is not required.

Nick.
--
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/