From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, tnt@246tNt.com
Subject: Re: [PATCH] powerpc: change rheap functions to use long integers instead of pointers
Date: Wed, 04 Apr 2007 12:42:50 -0500 [thread overview]
Message-ID: <4613E39A.70606@freescale.com> (raw)
In-Reply-To: <F4B76190-37C3-453C-B4F0-C1CB7CC0532E@kernel.crashing.org>
Kumar Gala wrote:
> I'm concerned the error handling isn't correctly. What happens if
> the rheap I'm managing has addresses at 0xf0000000. When I compare
> offset to 0, its going to report as an error, even if the offset
> returned is valid.
The return value is an offset INTO the actual buffer. Unless you have buffer larger than
2GB, the return value will never be negative unless it's an error. So technically, the
maximum size of the remote heap is 2GB. It doesn't matter where it was located.
Please keep in mind that I'm not changing the actual numeric values that are being
returned. I'm only changing the types, because they were wrong. rh_alloc() was returning
a void pointer, but it was NEVER a pointer. It was always a simple offset. The first
time you call rh_alloc(), you will get back a value of 0, because that's the beginning of
the heap. This patch doesn't change that. It changes the types.
Having said that, the code used to support heaps as large as 4GB - 4096, and now it
supports heaps as large as 2GB. I don't think that's a problem, but I can add a comment
to that effect in the changelog.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-04-04 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 16:02 [PATCH] powerpc: change rheap functions to use long integers instead of pointers Timur Tabi
2007-04-04 16:42 ` Kumar Gala
2007-04-04 17:36 ` Pantelis Antoniou
2007-04-04 17:42 ` Timur Tabi [this message]
2007-04-04 18:00 ` Sylvain Munaut
2007-04-04 18:05 ` Timur Tabi
2007-04-04 18:13 ` Timur Tabi
2007-04-04 19:15 ` Dan Malek
2007-04-04 19:20 ` Timur Tabi
2007-04-04 19:31 ` Sylvain Munaut
2007-04-04 18:13 ` Scott Wood
2007-04-04 18:19 ` Timur Tabi
2007-04-04 18:24 ` Scott Wood
2007-04-04 18:27 ` Timur Tabi
2007-04-04 18:31 ` Scott Wood
2007-04-04 18:34 ` Timur Tabi
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=4613E39A.70606@freescale.com \
--to=timur@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tnt@246tNt.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;
as well as URLs for NNTP newsgroup(s).