linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Anoop P.A." <Anoop_P.A@pmc-sierra.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: TITAN GE driver
Date: Wed, 2 Jun 2010 15:15:51 +0100	[thread overview]
Message-ID: <20100602141551.GA15753@linux-mips.org> (raw)
In-Reply-To: <A7DEA48C84FD0B48AAAE33F328C0201404E2DCA0@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>

On Wed, Jun 02, 2010 at 01:58:06AM -0700, Anoop P.A. wrote:

> [Anoop P.A.] You mean there are some flags available to force kmalloc to
> allocate memory below some address? I couldn't find one in kmalloc man
> pages.
> 
> BTW I am using 64 bit kernel.

There are:

 o GFP_DMA which usually means to allocate memory accessible to ISA DMA
   devices.
 o GFP_DMA32 which means memory in the low physical 4GB, that is memory
   accessible by 32-bit DMA devices.
 o GFP_HIGHMEM means any type of memory, even highmem.

All need to be explicitly supported by platform code which the existing
code doesn't.

Passing none of these flags would mean to allocate any non-highmem.  On
32-bit kernels that would be below 512MB physical but on 64-bit kernels
where there never is highmem it would just mean to allocate any memory.

I just hope the NIC isn't as braindead as you were describing but I got
no time to read up the docs again.

  Ralf

      parent reply	other threads:[~2010-06-02 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  5:51 TITAN GE driver Anoop P.A.
2010-05-28 16:27 ` Ralf Baechle
2010-06-02  8:10   ` Anoop P.A.
2010-06-02  8:10     ` Anoop P.A.
2010-06-02  8:32     ` Ralf Baechle
2010-06-02  8:58       ` Anoop P.A.
2010-06-02 13:48         ` Guenter Roeck
2010-06-02 14:02           ` Anoop P.A.
2010-06-02 14:15         ` Ralf Baechle [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=20100602141551.GA15753@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Anoop_P.A@pmc-sierra.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;
as well as URLs for NNTP newsgroup(s).