From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: wuming <wuming@ict.ac.cn>
Cc: linux-mips@linux-mips.org
Subject: Re: problem about dma
Date: Mon, 20 Dec 2004 21:14:16 +0800 [thread overview]
Message-ID: <41C6D028.5020004@ict.ac.cn> (raw)
In-Reply-To: <002101c4e679$72938bc0$6f64a8c0@spark>
I think that speculative loads may be the answer.
wuming wrote:
>----- Original Message -----
>From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
>To: "wuming" <wuming@ict.ac.cn>
>Cc: <linux-mips@linux-mips.org>
>Sent: Monday, December 20, 2004 4:43 PM
>Subject: Re: problem about dma
>
>
>
>
>>In 2.4, memcpy's prefetch may (and, in practice, do, no smiles, it cost
>>me a lot of time to realize) access that memory. I though it has been
>>fixed in 2.6 someday.
>>
>>Regards,
>>Gleb.
>>
>>
>>
>Thank you! :)
>But I think it is not the only reason, because the CPU on my platform does not
>support the "pref" instruction. So, memcpy's prefetch may have no effect on that
>arrange of memory.
>
>
>
prev parent reply other threads:[~2004-12-20 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 3:46 problem about dma wuming
2004-12-20 3:46 ` wuming
2004-12-20 8:43 ` Gleb O. Raiko
2004-12-20 9:51 ` wuming
2004-12-20 9:51 ` wuming
2004-12-20 13:14 ` Fuxin Zhang [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=41C6D028.5020004@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=wuming@ict.ac.cn \
/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