From: ebiederm@xmission.com (Eric W. Biederman)
To: Thomas Gleixner <tglx@linutronix.de>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Dmitry Safonov <dima@arista.com>,
Peter Zijlstra <peterz@infradead.org>,
Jeff Dike <jdike@addtoit.com>, Oleg Nesterov <oleg@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Andy Lutomirski <luto@kernel.org>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Adrian Reber <adrian@lisas.de>,
Pavel Emelianov <xemul@virtuozzo.com>
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Multiple time domains
Date: Thu, 01 Nov 2018 12:42:24 -0500 [thread overview]
Message-ID: <87ftwkpudb.fsf@xmission.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1811011407590.1642@nanos.tec.linutronix.de> (Thomas Gleixner's message of "Thu, 1 Nov 2018 14:21:26 +0100 (CET)")
Thomas Gleixner <tglx@linutronix.de> writes:
> Sorry for the late proposal, but this popped up recently.
>
> The recent discussion of the proposed time name spaces resulted in a larger
> range of questions how to handle that correctly. Aside of that we have
> other requests of supporting multiple time domains for various reasons,
> e.g. TSN folks in automotive and automation using grand clock masters with
> a completely screwed time base.
>
> As most of the relevant developers seem to be at LPC, I propose a technical
> session dedicated to discuss the handling of multiple time domains.
I will definitely be there.
To whoever schedules these things can we please have this one of the
days that overlaps LPC. So that all of the CRIU and container folks
have a chance to show up. Ideally not during the CRIU or Container mini
summit.
Eric
next prev parent reply other threads:[~2018-11-01 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 13:21 Thomas Gleixner
2018-11-01 17:33 ` Andy Lutomirski
2018-11-01 17:42 ` Eric W. Biederman [this message]
2018-11-01 20:09 ` Christian Brauner
2018-11-02 9:09 ` Pavel Emelianov
2018-11-03 17:13 ` Andrei Vagin
2018-11-03 18:47 ` Andy Tucker
2018-11-12 14:06 ` Dmitry Safonov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftwkpudb.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=adrian@lisas.de \
--cc=christian.brauner@ubuntu.com \
--cc=dima@arista.com \
--cc=gorcunov@openvz.org \
--cc=jdike@addtoit.com \
--cc=john.stultz@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=xemul@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox