[Top] [All Lists]

mb() calls in octeon / loongson swiotlb dma_map_ops

To: David Daney <>, Huacai Chen <>
Subject: mb() calls in octeon / loongson swiotlb dma_map_ops
From: Christoph Hellwig <>
Date: Sat, 30 Dec 2017 17:09:28 +0100
Cc: Hongliang Tao <>, Hua Yan <>, Alex Smith <>, Ralf Baechle <>, Rafał Miłecki <>,
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
User-agent: Mutt/1.5.17 (2007-11-01)
Hi David and others,

I've recently been refactoring the dma direct mapping and swiotlb
code, and one odd thing I noticed is that the octeon and loongson
swiotlb ops have mb() calls after basically all swiotlb calls.

None of that is explained in either the earlier octeon dma map
commits, nor the commit that added the octeon swiotlb support
(b93b2abce497873be97d765b848e0a955d29f200), and neither in the
loonsoon commit that apparently copy and pasted it

Can someone explain what these memory barrier are supposed to do?

<Prev in Thread] Current Thread [Next in Thread>
  • mb() calls in octeon / loongson swiotlb dma_map_ops, Christoph Hellwig <=