Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"

On Wed, Mar 15, 2006 at 02:31:14PM -0500, Vivek Goyal wrote:
> Is there a reason why "start" and "end" field of "struct resource" are of
> type unsigned long. My understanding is that "struct resource" can be used
> to represent any system resource including physical memory. But unsigned
> long is not suffcient to represent memory more than 4GB on PAE systems. 
> and compiler starts throwing warnings. 

Please make this depend on the kernel being compiled with PAE.  We don't 
need to bloat 32 bit kernels needlessly.

		-ben
-- 
"Time is of no importance, Mr. President, only life is important."
Don't Email: <[email protected]>.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
  - From: Kumar Gala <[email protected]>

References:
- [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
  - From: Vivek Goyal <[email protected]>

Prev by Date: Re: [RFC, PATCH 21/24] i386 Vmi proc node
Next by Date: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Previous by thread: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Next by thread: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]