public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] LINUX IA64 Memory Support
Date: Fri, 18 Feb 2000 05:27:52 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678204941@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204939@msgid-missing>

>>>>> On 15 Feb 2000 22:03:03 +0100, Jes Sorensen <Jes.Sorensen@cern.ch> said:

>>>>> "Venkatesh" = Venkatesh Ramamurthy <Venkateshr@ami.com> writes:
  Venkatesh> Hi, Is there any way in which one can allocate memory say
  Venkatesh> below 4 GB ( physical address )in drivers.  TIA Venkatesh

  Jes> This is not IA64 specific actually, so consider it a general
  Jes> answer rather than an IA64 one.

  Jes> A regular GFP_KERNEL should give you memory within the PCI
  Jes> DMA'able area, which with the old PCI system meant within the
  Jes> 4GB range. GFP_DMA will give you something within the ISA DMA
  Jes> space. However, in principle none of the above means that the
  Jes> memory is within the lower 4GB memory range, if the machine in
  Jes> question has an IOMMU type device, you may be handed memory
  Jes> which is in the middle of the memory space, but which is mapped
  Jes> to the 4GB the PCI bus in the machine can see.

  Jes> With the new PCI allocation system it is even more flexible,
  Jes> here you may get addresess anywhere and you then tell the PCI
  Jes> subsystem at run time to map the memory to the space the PCI
  Jes> bus can address. This means it will be possible to support
  Jes> systems with for instance 200 PCI busses (if someone feels like
  Jes> building such) etc.

Jes's answer is basically correct:

 - If you're writing a driver, use the new PCI DMA API (see pci.h in
   kernel 2.3.44 or later) and you'll be fine.

 - If you need memory below 4GB for some other reason, you're
   presently out of luck.  However, the already agreed upon solution
   is to add a new "zone" which will represent memory below 4GB
   (ZONE_32BIT or some such).  I plan to do this asap as we need this
   zone to properly implement the PCI DMA API (it currently works only
   because no Itanium system we know of/have access to has more than
   1GB of RAM ;-).

	--david



      parent reply	other threads:[~2000-02-18  5:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15 20:36 [Linux-ia64] LINUX IA64 Memory Support Venkatesh Ramamurthy
2000-02-15 21:03 ` Jes Sorensen
2000-02-18  5:27 ` David Mosberger [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=marc-linux-ia64-105590678204941@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@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