netdev - Re: [PATCH net-next] mlx4: do not use rwlock in fast path

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

Message-Id: <20170215.121039.185981521813042079.davem@davemloft.net>
Date:   Wed, 15 Feb 2017 12:10:39 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     eric.dumazet@...il.com
Cc:     netdev@...r.kernel.org, tariqt@...lanox.com,
        sbohrer@...advisors.com
Subject: Re: [PATCH net-next] mlx4: do not use rwlock in fast path

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Thu, 09 Feb 2017 09:10:04 -0800

> From: Eric Dumazet <edumazet@...gle.com>
> 
> Using a reader-writer lock in fast path is silly, when we can
> instead use RCU or a seqlock.
> 
> For mlx4 hwstamp clock, a seqlock is the way to go, removing
> two atomic operations and false sharing. 
> 
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

Applied, thanks Eric.