From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id 8A66D6B004D for ; Fri, 6 Nov 2009 11:30:12 -0500 (EST) Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e2.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id nA6GMRtm025455 for ; Fri, 6 Nov 2009 11:22:27 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id nA6GU8g1087116 for ; Fri, 6 Nov 2009 11:30:10 -0500 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id nA6GU7dp017329 for ; Fri, 6 Nov 2009 11:30:07 -0500 Date: Fri, 6 Nov 2009 08:30:07 -0800 From: "Paul E. McKenney" Subject: Re: [PATCHv7 3/3] vhost_net: a kernel-level virtio server Message-ID: <20091106163007.GC6746@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20091104115729.GD8398@redhat.com> <20091104172542.GC6736@linux.vnet.ibm.com> <200911061531.20299.rusty@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200911061531.20299.rusty@rustcorp.com.au> Sender: owner-linux-mm@kvack.org To: Rusty Russell Cc: "Michael S. Tsirkin" , Gregory Haskins , Eric Dumazet , netdev@vger.kernel.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org, akpm@linux-foundation.org, hpa@zytor.com, s.hetze@linux-ag.com List-ID: On Fri, Nov 06, 2009 at 03:31:20PM +1030, Rusty Russell wrote: > On Thu, 5 Nov 2009 03:55:42 am Paul E. McKenney wrote: > > On Wed, Nov 04, 2009 at 01:57:29PM +0200, Michael S. Tsirkin wrote: > > > Can you ack this usage please? > > > > I thought I had done so in my paragraph above, but if you would like > > something a bit more formal... > > > > That's great guys. And yes, this is a kind of read-copy-update. And no, > there's nothing wrong with it. > > But it's still nasty to use half an API. If it were a few places I would > have open-coded it with a comment, or wrapped it. As it is, I don't think > that would be a win. So would it help to have a rcu_read_lock_workqueue() and rcu_read_unlock_workqueue() that checked nesting and whether they were actually running in the context of a workqueue item? Or did you have something else in mind? Or am I misjudging the level of sarcasm in your reply? ;-) Thanx, Paul -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org