From: Ross Biro <ross.biro@gmail.com>
To: Matt Sexton <sexton@mc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DRAM and PCI devices at same physical address
Date: Mon, 28 Jun 2004 12:27:22 -0700 [thread overview]
Message-ID: <8783be6604062812277ee07aa@mail.gmail.com> (raw)
In-Reply-To: <1088198580.29697.62.camel@dhcp_client-120-140>
On 25 Jun 2004 17:23:00 -0400, Matt Sexton <sexton@mc.com> wrote:
>
> Should they be appearing there at all? Does Linux make any guarantees
> when there is more physical memory than specified by "mem=" ?
You've told linux there is only 512M of physical memory and it
believes you, so it is using the available address space for memory
mapped i/o. I know of no way to reserve memory on the command line.
next prev parent reply other threads:[~2004-06-28 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 21:23 DRAM and PCI devices at same physical address Matt Sexton
2004-06-27 3:26 ` Matt Porter
2004-06-28 15:51 ` Matt Sexton
2004-06-28 16:22 ` Matt Porter
2004-06-28 19:27 ` Ross Biro [this message]
2004-06-29 14:31 ` Matt Sexton
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=8783be6604062812277ee07aa@mail.gmail.com \
--to=ross.biro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sexton@mc.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