Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Zhuang Yuyao <mlistz@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [BUG?] cavium cn56xx and dma_map_single warning
Date: Mon, 22 Mar 2010 18:39:19 -0700	[thread overview]
Message-ID: <4BA81BC7.5060600@caviumnetworks.com> (raw)
In-Reply-To: <e732b6801003221830y2c2ca423tb67d74f7a3639c22@mail.gmail.com>

On 03/22/2010 06:30 PM, Zhuang Yuyao wrote:
> Thanks for your reply. Will this issue be solved soon? Is it a
> hardware issue or a software one?

A combination.  I think a Software fix is possible.

> Can I make the 4G-256M memory
> reserved so that kernel will not try to allocate memory in this area?
>

I have never tried it.

The issue is maintaining mappings for 32-bit PCI devices.  If you only 
want to support 64-bit devices, it would be easier to address the issue.

David Daney

> can not use more than 4G ram is bothersome since the memory is so cheap now. :-)
>
> Thanks very much.
>
> On Tue, Mar 23, 2010 at 12:44 AM, David Daney<ddaney@caviumnetworks.com>  wrote:
>>
>> This is a known issue.
>>
>> passing mem==3072M will restrict kernel memory usage thus avoiding the
>> issue.
>>
>> David Daney
>>
>

  reply	other threads:[~2010-03-23  1:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  7:01 [BUG?] cavium cn56xx and dma_map_single warning Zhuang Yuyao
2010-03-22  9:31 ` Zhuang Yuyao
2010-03-22 16:44 ` David Daney
2010-03-23  1:30   ` Zhuang Yuyao
2010-03-23  1:39     ` David Daney [this message]
2010-03-23  1:45       ` Zhuang Yuyao
2010-03-24 16:27         ` David Daney

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=4BA81BC7.5060600@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mlistz@gmail.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