From 4c275f208184aff5e933d49baf703d1aa23d8242 Mon Sep 17 00:00:00 2001 From: thorpej Date: Tue, 11 Feb 2003 07:02:26 +0000 Subject: [PATCH] Improve the wording regarding the relationship between bus_dmamap_sync() and memory barriers. --- share/man/man9/bus_dma.9 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/share/man/man9/bus_dma.9 b/share/man/man9/bus_dma.9 index d8465e4d91f9..6dcad8de6a75 100644 --- a/share/man/man9/bus_dma.9 +++ b/share/man/man9/bus_dma.9 @@ -1,4 +1,4 @@ -.\" $NetBSD: bus_dma.9,v 1.26 2003/01/28 01:07:51 kent Exp $ +.\" $NetBSD: bus_dma.9,v 1.27 2003/02/11 07:02:26 thorpej Exp $ .\" .\" Copyright (c) 1996, 1997, 1998, 2001 The NetBSD Foundation, Inc. .\" All rights reserved. @@ -445,9 +445,9 @@ See .Fn bus_dmamem_map for more information on this subject. .Pp -On platforms which implement reordered stores, +On platforms which implement a weak memory access ordering model, .Fn bus_dmamap_sync -will always cause the store buffer to be flushed. +will always cause the the appropriate memory barriers to be issued. .Pp This function exists to ensure that the host and the device have a consistent view of a range of DMA memory, before and after