From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752730AbcIIIAr (ORCPT ); Fri, 9 Sep 2016 04:00:47 -0400 Received: from relay6-d.mail.gandi.net ([217.70.183.198]:58432 "EHLO relay6-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751469AbcIIIAq (ORCPT ); Fri, 9 Sep 2016 04:00:46 -0400 X-Originating-IP: 50.39.163.18 Date: Fri, 9 Sep 2016 01:00:34 -0700 From: Josh Triplett To: Richard Cochran Cc: John Stultz , Nicolas Pitre , Thomas Gleixner , lkml Subject: Re: [RFC/PATCH] posix-timers: make them configurable Message-ID: <20160909080034.2cw7pnbu5vu7dc5j@x> References: <20160909074857.GA9083@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160909074857.GA9083@localhost.localdomain> User-Agent: NeoMutt/ (1.7.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 09, 2016 at 09:48:57AM +0200, Richard Cochran wrote: > On Thu, Sep 08, 2016 at 02:19:24PM -0700, John Stultz wrote: > > Also given many other syscalls take clockids and the backing logic > > isn't really getting removed (probably could cut the dynamic posix > > clocks core with the same conditional), I wonder if you could get a > > similar size win by taking a slightly more narrow cutting of the > > subsystem. That way you could preserve the more useful clock_gettime() > > functionality, but maybe stub out some of the less often used > > functionality. > > I want to support tinification, but I also doubt the utility of > removing clock_gettime() and clock_nanosleep(). I can't imagine ever > building a user space without those. In fact, thinking about IoT, > having good time is critical, and so these are the *last* functions I > would remove when downsizing. 1) If you already have another function providing time and don't need two. 2) If you run an entirely event-driven loop and don't sleep.