From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC][PATCH] srcu: Implement call_srcu()
Date: Tue, 31 Jan 2012 14:50:07 +0100
Message-ID: <1328017807.2446.230.camel@twins>
References: <1328016724.2446.229.camel@twins> <4F27F0E6.1040309@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
	Oleg Nesterov <oleg@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	KVM list <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <4F27F0E6.1040309@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Tue, 2012-01-31 at 15:47 +0200, Avi Kivity wrote:

> They really need to return quickly to userspace, and they really need to
> perform some operation between rcu_assign_pointer() and returning, so no.

Bugger :/

> >
> > Compile tested only!! :-)
> >
> 
> How much did synchronize_srcu_expedited() regress?  Presumably your
> compiler didn't tell you that.

Nope, quite a lot I figure.

> Can we get it back to speed by scheduling a work function on all cpus? 
> wouldn't that force a quiescent state and allow call_srcu() to fire?
> 
> In kvm's use case synchronize_srcu_expedited() is usually called when no
> thread is in a critical section, so we don't have to wait for anything
> except the srcu machinery.

OK, I'll try and come up with means of making it go fast again ;-)