From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753139AbbJOMaZ (ORCPT ); Thu, 15 Oct 2015 08:30:25 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:37432 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751380AbbJOMaY (ORCPT ); Thu, 15 Oct 2015 08:30:24 -0400 Date: Thu, 15 Oct 2015 14:30:21 +0200 From: Frederic Weisbecker To: George Spelvin Cc: jason.low2@hp.com, mingo@kernel.org, peterz@infradead.org, tglx@linutronix.de, akpm@linux-foundation.org, dave@stgolabs.net, hideaki.kimura@hpe.com, linux-kernel@vger.kernel.org, oleg@redhat.com, paulmck@linux.vnet.ibm.com, rostedt@goodmis.org, scott.norton@hpe.com, terry.rudd@hpe.com Subject: Re: [PATCH v2 0/4] timer: Improve itimers scalability Message-ID: <20151015123018.GA12822@lerouge> References: <1444849677-29330-1-git-send-email-jason.low2@hp.com> <20151014211827.739.qmail@ns.horizon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151014211827.739.qmail@ns.horizon.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 14, 2015 at 05:18:27PM -0400, George Spelvin wrote: > I'm going to give 4/4 a closer look to see if the races with timer > expiration make more sense to me than last time around. > (E.g. do CPU time signals even work in CONFIG_NO_HZ_FULL?) Those enqueued with timer_settime() do work. But itimers, and rlimits (RLIMIT_RTTIME, RLIMIT_CPU) aren't supported well. I need to rework that. > > But although I haven't yet convinced myself the current code is right, > the changes don't seem to make it any worse. So consider all four > > Reviewed-by: George Spelvin > > Thank you!