From: Jim Blandy <jimb@codesourcery.com>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: Non-uniform address spaces
Date: Tue, 26 Jun 2007 17:55:00 -0000 [thread overview]
Message-ID: <m3k5tqtxcf.fsf@codesourcery.com> (raw)
In-Reply-To: <46814B4C.7080302@eagercon.com> (Michael Eager's message of "Tue, 26 Jun 2007 10:22:20 -0700")
Michael Eager <eager@eagercon.com> writes:
>>> One problem may be that it may not be clear whether one has a
>>> pointer to a linear code space or to a distributed NUMA data space.
>>> It might be reasonable to model the linear code space as a 64-bit
>>> CORE_ADDR, with the top half zero, while a NUMA address has non-zero
>>> values in the top half. (I don't know if there might be alias
>>> problems, where zero might be valid for the top half of a NUMA address.)
>>
>> I think this isn't going to be a problem, but it's hard to tell. Can
>> you think of a specific case where we wouldn't be able to tell which
>> we have?
>
> Only if the <processor,thread> component of a NUMA address can be
> zero, and looks like a linear address.
I guess what I've been getting at is, why do we need to represent both
NUMA and linear addresses? If linear addresses refer to specific
subsets of the grand unified NUMA address space, then we should simply
declare CORE_ADDR to hold NUMA addresses, and make sure that linear
addresses always get converted to NUMA addresses at a point where we
have enough context to do so.
next prev parent reply other threads:[~2007-06-26 17:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 16:31 Michael Eager
2007-06-23 21:25 ` Daniel Jacobowitz
2007-06-23 21:47 ` Michael Eager
2007-06-23 23:09 ` Daniel Jacobowitz
2007-06-25 17:46 ` Jim Blandy
2007-06-25 18:08 ` Michael Eager
2007-06-25 19:05 ` Jim Blandy
2007-06-25 19:09 ` Daniel Jacobowitz
2007-06-25 20:04 ` Michael Eager
2007-06-25 22:23 ` Jim Blandy
2007-06-25 22:55 ` Michael Eager
2007-06-25 23:08 ` basic gdb usage question Matt Funk
[not found] ` <655C3D4066B7954481633935A40BB36F041415@ussunex02.svl.access-company.com>
2007-06-25 23:36 ` Matt Funk
2007-06-26 1:25 ` Michael Eager
2007-06-26 3:12 ` Eli Zaretskii
2007-06-26 16:13 ` Matt Funk
2007-06-27 3:29 ` Eli Zaretskii
2007-06-26 16:56 ` Non-uniform address spaces Jim Blandy
2007-06-26 17:22 ` Michael Eager
2007-06-26 17:55 ` Jim Blandy [this message]
2007-06-26 18:08 ` Jim Blandy
2007-06-26 23:08 ` Michael Eager
2007-06-26 23:39 ` Jim Blandy
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=m3k5tqtxcf.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.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