From: Ben Johnson <ben@blarg.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linear vs. logical addresses? how does cpu interpret kernel addrs?
Date: Tue, 16 Sep 2003 18:44:21 -0700 [thread overview]
Message-ID: <20030916184421.A25733@blarg.net> (raw)
In-Reply-To: <1563260000.1063760286@[10.10.2.4]>; from mbligh@aracnet.com on Tue, Sep 16, 2003 at 05:58:08PM -0700
On Tue, Sep 16, 2003 at 05:58:08PM -0700, Martin J. Bligh wrote:
>
> BTW, to the original question ... chapter 2 of "Understanding the Linux Kernel"
> had a good explanation of all this.
Thank you. I've been reading the first addition. is there a second?
the second chapter has a very good explanation of paging and how linear
addresses are used. logical addresses on the other hand are barely
mentioned. Segmentation is described well, but the translation of
logical into linear addresses is not described.
I've read elsewhere that logical addresses are comprised of a 16-bit
segment selector and a 32-bit offset. I thought pointers were always
exactly 32-bits (on 32-bit intel). where is the 16-bit selector?
Thanks again.
- Ben
next prev parent reply other threads:[~2003-09-17 1:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 22:47 linear vs. logical addresses? how does cpu interpret kernel addrs? Ben Johnson
2003-09-17 0:48 ` Martin J. Bligh
2003-09-17 0:54 ` William Lee Irwin III
2003-09-17 0:58 ` Martin J. Bligh
2003-09-17 1:44 ` Ben Johnson [this message]
2003-09-17 1:55 ` William Lee Irwin III
2003-09-17 2:07 ` Ben Johnson
2003-09-17 2:10 ` William Lee Irwin III
2003-09-17 2:32 ` Ben Johnson
2003-09-17 2:10 ` Felipe Alfaro Solana
2003-09-17 11:39 ` Richard B. Johnson
2003-09-17 19:42 ` Ben Johnson
2003-09-17 20:05 ` Richard B. Johnson
2003-09-17 20:44 ` Jamie Lokier
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=20030916184421.A25733@blarg.net \
--to=ben@blarg.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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