netdev - Re: [net-next PATCH 0/3] Replace wmb()/rmb() with dma_wmb()/dma

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-prev] [day] [month] [year] [list]

Message-Id: <20150408.121531.264247541235587759.davem@davemloft.net>
Date:	Wed, 08 Apr 2015 12:15:31 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	alexander.h.duyck@...hat.com
Cc:	netdev@...r.kernel.org
Subject: Re: [net-next PATCH 0/3] Replace wmb()/rmb() with
 dma_wmb()/dma_rmb() where appropriate

From: Alexander Duyck <alexander.h.duyck@...hat.com>
Date: Tue, 07 Apr 2015 16:55:08 -0700

> This is a start of a side project cleaning up the drivers that can make use
> of the dma_wmb and dma_rmb calls.  The general idea is to start removing
> the unnecessary wmb/rmb calls from a number of drivers and to make use of
> the lighter weight dma_wmb/dma_rmb calls as this should allow for an
> overall improvement in performance as each barrier can cost a significant
> number of cycles and on architectures such as x86 this is unnecessary.
> 
> These changes are what I would consider low hanging fruit.  The likelihood
> of the changes introducing an error should be low since the use of the
> barriers in these cases are fairly obvious.

Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html