From: Benjamin LaHaise <bcrl@kvack.org>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Fastboot mailing list <fastboot@lists.osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Morton Andrew Morton <akpm@osdl.org>,
gregkh@suse.de
Subject: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Date: Wed, 15 Mar 2006 15:53:06 -0500 [thread overview]
Message-ID: <20060315205306.GC25361@kvack.org> (raw)
In-Reply-To: <20060315193114.GA7465@in.ibm.com>
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: <dont@kvack.org>.
next prev parent reply other threads:[~2006-03-15 20:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 19:31 [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource" Vivek Goyal
2006-03-15 19:48 ` Kumar Gala
2006-03-15 19:57 ` Arjan van de Ven
2006-03-15 20:01 ` Kumar Gala
2006-03-15 20:10 ` Kumar Gala
2006-03-15 20:13 ` Eric W. Biederman
2006-03-15 20:28 ` Kumar Gala
2006-03-15 20:37 ` Eric W. Biederman
2006-03-15 20:32 ` Vivek Goyal
2006-03-15 20:58 ` Eric W. Biederman
2006-03-15 21:57 ` David S. Miller
2006-03-15 20:53 ` Benjamin LaHaise [this message]
2006-03-15 21:05 ` Kumar Gala
2006-03-15 21:13 ` Benjamin LaHaise
2006-03-15 21:29 ` Eric W. Biederman
2006-03-15 21:28 ` Benjamin LaHaise
2006-03-15 21:50 ` Eric W. Biederman
2006-03-15 22:13 ` Andrew Morton
2006-03-15 22:18 ` David S. Miller
2006-03-15 21:59 ` Eric W. Biederman
2006-03-15 22:07 ` Benjamin LaHaise
2006-03-16 14:45 ` Eric W. Biederman
2006-03-15 21:30 ` Kumar Gala
2006-03-15 21:35 ` hackmiester / Hunter Fuller
2006-03-15 21:31 ` Eric W. Biederman
2006-03-15 21:15 ` Eric W. Biederman
2006-03-15 21:26 ` linux-os (Dick Johnson)
2006-03-15 21:37 ` Eric W. Biederman
2006-03-15 22:08 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060315205306.GC25361@kvack.org \
--to=bcrl@kvack.org \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox