From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753852Ab0BGJmq (ORCPT ); Sun, 7 Feb 2010 04:42:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38592 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753077Ab0BGJmo (ORCPT ); Sun, 7 Feb 2010 04:42:44 -0500 Message-ID: <4B6E8B05.8070607@redhat.com> Date: Sun, 07 Feb 2010 11:42:29 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 MIME-Version: 1.0 To: "Michael S. Tsirkin" CC: Rusty Russell , kvm@vger.kernel.org, virtualization@lists.osdl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, David Miller Subject: Re: [PATCH] vhost-net: switch to smp barriers References: <20100201172101.GA10900@redhat.com> In-Reply-To: <20100201172101.GA10900@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -- error compiling committee.c: too many arguments to function