From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Memory-mapped I/O barriers, state of affairs?
Date: Mon, 22 Mar 2010 20:18:49 +0100 [thread overview]
Message-ID: <c384c5ea1003221218o2dfcf445s8b7fd5c08076bdab@mail.gmail.com> (raw)
Hello,
searching for good info on device IO racing against host memory writes
I came upon this 2006 article:
http://lwn.net/Articles/198988/
"there is no guaranteed ordering between writes to regular memory and
writes to a memory-mapped I/O range. "
What is the current solution for that particular problem, i.e. how
should I make sure host memory writes are committed before I have an
external DMA device act on it?
Thanks,
--
Leon Woestenberg.
next reply other threads:[~2010-03-22 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 19:18 Leon Woestenberg [this message]
2010-03-22 20:16 ` Andreas Bombe
2010-03-22 22:12 ` Leon Woestenberg
2010-03-23 0:14 ` Robert Hancock
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=c384c5ea1003221218o2dfcf445s8b7fd5c08076bdab@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome