Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752290Ab0LZOPE (ORCPT ); Sun, 26 Dec 2010 09:15:04 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:39347 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752175Ab0LZOPB (ORCPT ); Sun, 26 Dec 2010 09:15:01 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=tLRmS3RRwpUlssl42M1TEk5FbSEs/ETc0JOCTKxVsQ0FTYKy32hu64tErNgilewLvx xKP+KMagWolvF6rC+VS5N+wycs65xIzrvlSOoRJDcSgENlkI3WdbCppMtTkCOlrsct4c ugOvbGZWLmpw6iSzDKQfnsdjnglawCpFnixhU= Date: Sun, 26 Dec 2010 15:14:47 +0100 From: Richard Cochran To: "Kuwahara,T." <6vvetjsrt26xsrzlh1z0zn4d2grdah@gmail.com> Cc: john stultz , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, netdev@vger.kernel.org, Alan Cox , Arnd Bergmann , Christoph Lameter , David Miller , Krzysztof Halasa , Peter Zijlstra , Rodolfo Giometti , Thomas Gleixner Subject: Re: [PATCH V7 1/8] ntp: add ADJ_SETOFFSET mode bit Message-ID: <20101226141447.GA4830@riccoc20.at.omicron.at> References: <880d82bb8120f73973db27e0c48e949014b1a106.1292512461.git.richard.cochran@omicron.at> <20101221075612.GA13626@riccoc20.at.omicron.at> <1292970355.2618.76.camel@work-vm> <20101223061359.GA7169@riccoc20.at.omicron.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1406 Lines: 30 On Sun, Dec 26, 2010 at 05:38:57AM +0900, Kuwahara,T. wrote: > After all, I'd prefer your earlier patchset. Leaving aside the > compatibility issue, there's no particular reason we have to re-use > the struct timex, which requires otherwise unnecessary conditional > branches as well as unit conversions. Don't you agree? Well, from my point of view of wanting to allow a user space clock servo to be able to adjust a hardware clock, it would be sufficient to offer a way to jump the clock and to adjust the frequency via one or perhaps two new system calls. That is indeed what I first suggested, and I still think it would be a clean and simple interface. The NTP call is quite gross, since it multiplexes a whole bunch of different functions through the timex structure. However, several reviewers on the lkml prefered to keep with the NTP interface. It offers the needed functionality and is already well established, despite its ugliness. To me, the proposed ADJ_SETOFFSET is a simple and logical extenstion of the NTP interface. Also, the implementation is straightforward. In contrast, using a special -INF value seems a bit obtuse to me. Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/