From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: wuming <wuming@ict.ac.cn>
Cc: linux-mips@linux-mips.org
Subject: Re: problem about dma
Date: Mon, 20 Dec 2004 11:43:59 +0300 [thread overview]
Message-ID: <41C690CF.2010306@niisi.msk.ru> (raw)
In-Reply-To: <001501c4e646$7f676c00$6f64a8c0@spark>
wuming wrote:
> Before the dma transfer, pci_map_sg will map the memory space covered by sg_table,
> and it will flush and invalidate cache indexed by that memory space.
> After the dma transfer, pci_unmap_sg also needs to be called to flush and invalidate
> the same cache. But I do not know why the second flush will be demanded.
> I think that in the interval between the two flush, there would be nothing to access
> the memory covered by the dma. But it is not the case.
> I want to know what can access that memory and I need some help.
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.
next prev parent reply other threads:[~2004-12-20 8:46 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 [this message]
2004-12-20 9:51 ` wuming
2004-12-20 9:51 ` wuming
2004-12-20 13:14 ` Fuxin Zhang
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=41C690CF.2010306@niisi.msk.ru \
--to=raiko@niisi.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.