From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH 4/6] kvm tools: Add rwlock wrapper Date: Fri, 27 May 2011 15:07:56 +0200 Message-ID: <20110527130756.GA3415@elte.hu> References: <1306419950-19064-1-git-send-email-levinsasha928@gmail.com> <1306419950-19064-4-git-send-email-levinsasha928@gmail.com> <1306426743.3065.34.camel@lappy> <20110526180518.GA3572@elte.hu> <4DDE97CE.4000302@redhat.com> <20110526202531.GA2765@elte.hu> <20110526230508.GA15983@Krystal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Pekka Enberg , Avi Kivity , Sasha Levin , john@jfloren.net, kvm@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com, prasadjoshi124@gmail.com, "Paul E. McKenney" To: Mathieu Desnoyers Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:33922 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753688Ab1E0NIP (ORCPT ); Fri, 27 May 2011 09:08:15 -0400 Content-Disposition: inline In-Reply-To: <20110526230508.GA15983@Krystal> Sender: kvm-owner@vger.kernel.org List-ID: * Mathieu Desnoyers wrote: > > instead of bringing in yet another library which is a IIRC a > > distant copy of the kernel code to begin with. > > This is either a lie, or immensely misinformed. You should go and > look at the source before doing nonsensical assumptions like this. > What you are saying cannot be further from the truth. I was merely immensely misinformed, which (distinct!) possibility i tried to signal via the 'IIRC' qualifier as well ;-) While right now i cannot clone the repository itself: $ git clone git://git.lttng.org/urcu Cloning into urcu... fatal: The remote end hung up unexpectedly (tried it several times today, same failure) I found a tarball of the package so could have a look again. Despite my initial impression of it being kernel RCU code related (it has system.h, smp_mb, list_head, etc.), a closer look indeed suggests that the RCU implementation itself does not use the kernel RCU concepts so it sadly cannot be a distant copy of the kernel RCU code! Which is too bad IMO: i don't think user-space RCU should necessarily be so different from kernel-space RCU. I think the two codebases could be shared, or at least they could become closer relatives! :-) That could be done using the migration event notification trick i suggested in the previous mail. Thanks, Ingo