Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Finney, Steve" <Steve.Finney@SpirentCom.COM>
Cc: linux-mips@linux-mips.org
Subject: Re: kmalloc question
Date: Thu, 9 Oct 2003 10:09:40 +0200	[thread overview]
Message-ID: <20031009080940.GC19372@linux-mips.org> (raw)
In-Reply-To: <DC1BF43A8FAE654DA6B3FB7836DD3A56DEB76D@iris.adtech-inc.com>

On Wed, Oct 08, 2003 at 03:06:50PM -1000, Finney, Steve wrote:

> Is kmalloc (GFP_KERNEL) on a 32 bit HIGHMEM enabled MIPS kernel (BCM/Sibyte processor) guaranteed to allocate memory from the low, KSEG0/1 addressible region? I'm having trouble sorting through the slab.c code. On this processor, only 256 MB of DRAM is directly addressible; with more than 256 MB of RAM, there is 256 MB in zone 0, and the remainder in zone 2. Zone 1 is empty.

Yes.

  Ralf

  parent reply	other threads:[~2003-10-09  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09  1:06 kmalloc question Finney, Steve
2003-10-09  1:06 ` Finney, Steve
2003-10-09  8:09 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-05  5:25 Andre.Messerschmidt
2002-06-05 17:24 ` Alan Cox

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=20031009080940.GC19372@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Steve.Finney@SpirentCom.COM \
    --cc=linux-mips@linux-mips.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