From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC] virtio_net: add local_bh_disable() around u64_stats_update_begin Date: Tue, 16 Oct 2018 11:01:14 -0700 Message-ID: <20181016110114.73e2b248__8686.69576379961$1539712811$gmane$org@xeon-e3> References: <20181016165545.guksrl23ulcudxrk@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20181016165545.guksrl23ulcudxrk@linutronix.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Sebastian Andrzej Siewior Cc: "Michael S. Tsirkin" , netdev@vger.kernel.org, virtualization@lists.linux-foundation.org, tglx@linutronix.de, "David S. Miller" List-Id: virtualization@lists.linuxfoundation.org On Tue, 16 Oct 2018 18:55:45 +0200 Sebastian Andrzej Siewior wrote: > Also, ptr->var++ is not an atomic operation even on 64bit CPUs. Which > means if try_fill_recv() runs on CPU0 (via virtnet_receive()) then the > worker might run on CPU1. On modern CPU's increment of native types is atomic but not locked. u64_stats_update_begin is a no-op on UP and also if BIT_PER_LONG != 32