From: Daniel Jacobowitz <drow@false.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: Non-uniform address spaces
Date: Sat, 23 Jun 2007 23:09:00 -0000 [thread overview]
Message-ID: <20070623231001.GA8183@caradoc.them.org> (raw)
In-Reply-To: <467D9503.9060804@eagercon.com>
On Sat, Jun 23, 2007 at 02:47:47PM -0700, Michael Eager wrote:
> I thought most of the HA systems just increased the address size by
> one bit and had the high-order bit specify whether the address
> was in D or I address space.
That's more or less what I said :-) It's a simpler mapping than
yours, but still the same approach. However, you need a lot more bits
than they do.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-23 23:09 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 [this message]
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
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=20070623231001.GA8183@caradoc.them.org \
--to=drow@false.org \
--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