Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758272AbZAUOm1 (ORCPT ); Wed, 21 Jan 2009 09:42:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754781AbZAUOmQ (ORCPT ); Wed, 21 Jan 2009 09:42:16 -0500 Received: from mga01.intel.com ([192.55.52.88]:35952 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753648AbZAUOmO (ORCPT ); Wed, 21 Jan 2009 09:42:14 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.37,300,1231142400"; d="scan'208";a="658911906" Subject: Re: [PATCH NET-NEXT 11/12] time sync: generic infrastructure to map between time stamps generated by a time counter and system time From: Patrick Ohly To: Ingo Molnar Cc: Thomas Gleixner , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , David Miller , "linux-api@vger.kernel.org" In-Reply-To: <20090121103330.GA25531@elte.hu> References: <1232532612-10382-2-git-send-email-patrick.ohly@intel.com> <1232532612-10382-3-git-send-email-patrick.ohly@intel.com> <1232532612-10382-4-git-send-email-patrick.ohly@intel.com> <1232532612-10382-5-git-send-email-patrick.ohly@intel.com> <1232532612-10382-6-git-send-email-patrick.ohly@intel.com> <1232532612-10382-7-git-send-email-patrick.ohly@intel.com> <1232532612-10382-8-git-send-email-patrick.ohly@intel.com> <1232532612-10382-9-git-send-email-patrick.ohly@intel.com> <1232532612-10382-10-git-send-email-patrick.ohly@intel.com> <1232532612-10382-11-git-send-email-patrick.ohly@intel.com> <20090121103330.GA25531@elte.hu> Content-Type: text/plain Date: Wed, 21 Jan 2009 15:42:10 +0100 Message-Id: <1232548930.13393.24.camel@ecld0pohly> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2000 Lines: 44 On Wed, 2009-01-21 at 10:33 +0000, Ingo Molnar wrote: > * Patrick Ohly wrote: > > > Currently only mapping from time counter to system time is implemented. > > The interface could have been made more versatile by not depending on a time counter, > > but this wasn't done to avoid writing glue code elsewhere. > > > > The method implemented here is the one used and analyzed under the name > > "assisted PTP" in the LCI PTP paper: > > http://www.linuxclustersinstitute.org/conferences/archive/2008/PDF/Ohly_92221.pdf > > --- > > include/linux/clocksync.h | 85 +++++++++++++++++++ > > kernel/time/Makefile | 2 +- > > kernel/time/clocksync.c | 196 +++++++++++++++++++++++++++++++++++++++++++++ > > 3 files changed, 282 insertions(+), 1 deletions(-) > > create mode 100644 include/linux/clocksync.h > > create mode 100644 kernel/time/clocksync.c > > hm, these bits have less than casual impact - i think they need to go via > the timer tree. I agree that they should be reviewed by experts in that area. Patch 11 and 09 (which 11 depends on and which was already reviewed by John) are independent of the rest of the patch series and could be included in the timer tree. On the other hand that code is only called by the example igb driver in this patch series, which won't compile without the timer changes. Please let me know if I should pursue the inclusion separately and if so, how the inclusion of the two trees can be coordinated. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- 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/