linux-kernel - Memory-mapped I/O barriers, state of affairs?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <c384c5ea1003221218o2dfcf445s8b7fd5c08076bdab@mail.gmail.com>
Date:	Mon, 22 Mar 2010 20:18:49 +0100
From:	Leon Woestenberg <leon.woestenberg@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Memory-mapped I/O barriers, state of affairs?

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/