From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH] vhost-net: switch to smp barriers Date: Sun, 7 Feb 2010 11:44:42 +0200 Message-ID: <20100207094441.GA20271@redhat.com> References: <20100201172101.GA10900@redhat.com> <4B6E8B05.8070607@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Rusty Russell , kvm@vger.kernel.org, virtualization@lists.osdl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, David Miller To: Avi Kivity Return-path: Content-Disposition: inline In-Reply-To: <4B6E8B05.8070607@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Sun, Feb 07, 2010 at 11:42:29AM +0200, Avi Kivity wrote: > On 02/01/2010 07:21 PM, Michael S. Tsirkin wrote: >> vhost-net only uses memory barriers to control SMP effects >> (communication with userspace potentially running on a different CPU), >> so it should use SMP barriers and not mandatory barriers for memory >> access ordering, as suggested by Documentation/memory-barriers.txt >> >> > > A UP guest running on an SMP host still needs those barriers. Correct. And since vhost net is running host-side, smp_XX barriers will do exactly the right thing, right? > -- > error compiling committee.c: too many arguments to function