[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090121103330.GA25531@elte.hu>
Date: Wed, 21 Jan 2009 11:33:30 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Patrick Ohly <patrick.ohly@...el.com>,
Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
David Miller <davem@...emloft.net>, linux-api@...r.kernel.org
Subject: Re: [PATCH NET-NEXT 11/12] time sync: generic infrastructure to
map between time stamps generated by a time counter and system time
* Patrick Ohly <patrick.ohly@...el.com> 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.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists