Linux-assembly Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Raiter <breadbox@muppetlabs.com>
To: linux-assembly@vger.kernel.org
Subject: Re: Segment override and lldt instruction
Date: Sun, 10 Jun 2007 22:30:43 -0700	[thread overview]
Message-ID: <18028.56835.820833.299934@eidolon.muppetlabs.com> (raw)
In-Reply-To: <BAY133-F2621988146A83572C34FFBF51A0@phx.gbl>

> So if answer is yes, and if more than 4GB of memory space is needed
> for a program how will segmentation register go beyond 4gig without
> override?

A single process cannot access more than 4GB in 32-bit Linux. Period.
If you need more than 4GB, then you should be using 64-bit Linux.

b

      parent reply	other threads:[~2007-06-11  5:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 22:31 Segment override and lldt instruction A D
2007-05-31  0:45 ` Frank Kotler
2007-05-31  1:21   ` A D
2007-06-04 23:52   ` Hendrik Visage
2007-06-11  0:33     ` A D
2007-06-11  1:14       ` Frank Kotler
2007-06-11  5:30       ` Brian Raiter [this message]

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=18028.56835.820833.299934@eidolon.muppetlabs.com \
    --to=breadbox@muppetlabs.com \
    --cc=linux-assembly@vger.kernel.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).