From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932582AbcHIMoe (ORCPT ); Tue, 9 Aug 2016 08:44:34 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:37149 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932498AbcHIMoa (ORCPT ); Tue, 9 Aug 2016 08:44:30 -0400 Date: Tue, 9 Aug 2016 14:44:26 +0200 From: Peter Zijlstra To: Davidlohr Bueso Cc: akpm@linux-foundation.org, manfred@colorfullife.com, bigeasy@linutronix.de, tglx@linutronix.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/5] ipc/msg: Sender/receiver optimizations Message-ID: <20160809124426.GE7141@twins.programming.kicks-ass.net> References: <1469748819-19484-1-git-send-email-dave@stgolabs.net> <20160804164409.GS6862@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160804164409.GS6862@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 04, 2016 at 06:44:09PM +0200, Peter Zijlstra wrote: > On Thu, Jul 28, 2016 at 04:33:34PM -0700, Davidlohr Bueso wrote: > > Hi, > > > > I'm resending Sebastian's sysv msg queue use of wake_qs but updated > > to the last observations I need wrt the need of explicit barriers > > after removing the whole receiver busy-looping. After some irc exchange > > it seems we're both on the same page, and things now look like he had > > them earlier, in v2. This is all patch 1. > > > > The rest of the patches are changes I noticed while reviewing patch 1, > > which are mainly sender-side rework/optimizations. Details are in each > > changelog. > > > > The changes have survived ltp (which has some nasty corner cases for msgsnd > > changes), as well as pmsg-shared benchmark. > > Not really my area, but over all the patches look good. > > Acked-by: Peter Zijlstra (Intel) Andrew, will you pick these up, or should I route then through tip/locking or something?