From: 0x7f454c46 at gmail.com (Dmitry Safonov)
Subject: [RFC 00/20] ns: Introduce Time Namespace
Date: Wed, 26 Sep 2018 18:59:49 +0100 [thread overview]
Message-ID: <CAJwJo6bseG42YNqA0cxWpB0C252_CWER0gDrF0OUOm+=DJ7XdQ@mail.gmail.com> (raw)
In-Reply-To: <87zhw4rwiq.fsf@xmission.com>
2018-09-26 18:36 GMT+01:00 Eric W. Biederman <ebiederm at xmission.com>:
> The advantage of timekeeping_update per time namespace is that it allows
> different lengths of seconds per time namespace. Which allows testing
> ntp and the kernel in interesting ways while still having a working
> production configuration on the same system.
Just a quick note: the different length of second per namespace sounds
very interesting in my POV, I remember I've seen this article:
http://publish.illinois.edu/science-of-security-lablet/files/2014/05/DSSnet-A-Smart-Grid-Modeling-Platform-Combining-Electrical-Power-Distributtion-System-Simulation-and-Software-Defined-Networking-Emulation.pdf
And their realisation with a simulation of time going with different speed
per-pid (with vdso disabled):
https://github.com/littlepretty/VirtualTimeKernel
Thanks,
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: 0x7f454c46@gmail.com (Dmitry Safonov)
Subject: [RFC 00/20] ns: Introduce Time Namespace
Date: Wed, 26 Sep 2018 18:59:49 +0100 [thread overview]
Message-ID: <CAJwJo6bseG42YNqA0cxWpB0C252_CWER0gDrF0OUOm+=DJ7XdQ@mail.gmail.com> (raw)
Message-ID: <20180926175949.JvM_3dFgRHJpO4PT_G605bce1gQz8us_vatkpRAKFR0@z> (raw)
In-Reply-To: <87zhw4rwiq.fsf@xmission.com>
2018-09-26 18:36 GMT+01:00 Eric W. Biederman <ebiederm at xmission.com>:
> The advantage of timekeeping_update per time namespace is that it allows
> different lengths of seconds per time namespace. Which allows testing
> ntp and the kernel in interesting ways while still having a working
> production configuration on the same system.
Just a quick note: the different length of second per namespace sounds
very interesting in my POV, I remember I've seen this article:
http://publish.illinois.edu/science-of-security-lablet/files/2014/05/DSSnet-A-Smart-Grid-Modeling-Platform-Combining-Electrical-Power-Distributtion-System-Simulation-and-Software-Defined-Networking-Emulation.pdf
And their realisation with a simulation of time going with different speed
per-pid (with vdso disabled):
https://github.com/littlepretty/VirtualTimeKernel
Thanks,
Dmitry
next prev parent reply other threads:[~2018-09-26 17:59 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 20:50 [RFC 00/20] ns: Introduce Time Namespace dima
2018-09-19 20:50 ` Dmitry Safonov
2018-09-19 20:50 ` [RFC 16/20] selftest: Add Time Namespace test for supported clocks dima
2018-09-19 20:50 ` Dmitry Safonov
2018-09-24 21:36 ` shuah
2018-09-24 21:36 ` Shuah Khan
2018-09-19 20:50 ` [RFC 17/20] selftest/timens: Add test for timerfd dima
2018-09-19 20:50 ` Dmitry Safonov
2018-09-19 20:50 ` [RFC 18/20] selftest/timens: Add test for clock_nanosleep dima
2018-09-19 20:50 ` Dmitry Safonov
2018-09-19 20:50 ` [RFC 19/20] timens/selftest: Add procfs selftest dima
2018-09-19 20:50 ` Dmitry Safonov
2018-09-19 20:50 ` [RFC 20/20] timens/selftest: Add timer offsets test dima
2018-09-19 20:50 ` Dmitry Safonov
2018-09-21 12:27 ` [RFC 00/20] ns: Introduce Time Namespace ebiederm
2018-09-21 12:27 ` Eric W. Biederman
2018-09-24 20:51 ` avagin
2018-09-24 20:51 ` Andrey Vagin
2018-09-24 22:02 ` ebiederm
2018-09-24 22:02 ` Eric W. Biederman
2018-09-25 1:42 ` avagin
2018-09-25 1:42 ` Andrey Vagin
2018-09-26 17:36 ` ebiederm
2018-09-26 17:36 ` Eric W. Biederman
2018-09-26 17:59 ` 0x7f454c46 [this message]
2018-09-26 17:59 ` Dmitry Safonov
2018-09-27 21:30 ` tglx
2018-09-27 21:30 ` Thomas Gleixner
2018-09-27 21:41 ` tglx
2018-09-27 21:41 ` Thomas Gleixner
2018-10-01 23:20 ` avagin
2018-10-01 23:20 ` Andrey Vagin
2018-10-02 6:15 ` tglx
2018-10-02 6:15 ` Thomas Gleixner
2018-10-02 21:05 ` 0x7f454c46
2018-10-02 21:05 ` Dmitry Safonov
2018-10-02 21:26 ` tglx
2018-10-02 21:26 ` Thomas Gleixner
2018-09-28 17:03 ` ebiederm
2018-09-28 17:03 ` Eric W. Biederman
2018-09-28 19:32 ` tglx
2018-09-28 19:32 ` Thomas Gleixner
2018-10-01 9:05 ` ebiederm
2018-10-01 9:05 ` Eric W. Biederman
2018-10-01 9:15 ` Setting monotonic time? ebiederm
2018-10-01 9:15 ` Eric W. Biederman
2018-10-01 18:52 ` tglx
2018-10-01 18:52 ` Thomas Gleixner
2018-10-02 20:00 ` arnd
2018-10-02 20:00 ` Arnd Bergmann
2018-10-02 20:06 ` tglx
2018-10-02 20:06 ` Thomas Gleixner
2018-10-03 4:50 ` ebiederm
2018-10-03 4:50 ` Eric W. Biederman
2018-10-03 5:25 ` tglx
2018-10-03 5:25 ` Thomas Gleixner
2018-10-03 6:14 ` ebiederm
2018-10-03 6:14 ` Eric W. Biederman
2018-10-03 7:02 ` arnd
2018-10-03 7:02 ` Arnd Bergmann
2018-10-03 6:14 ` tglx
2018-10-03 6:14 ` Thomas Gleixner
2018-10-01 20:51 ` avagin
2018-10-01 20:51 ` Andrey Vagin
2018-10-02 6:16 ` tglx
2018-10-02 6:16 ` Thomas Gleixner
2018-10-21 1:41 ` [RFC 00/20] ns: Introduce Time Namespace avagin
2018-10-21 1:41 ` Andrei Vagin
2018-10-21 3:54 ` avagin
2018-10-21 3:54 ` Andrei Vagin
2018-10-29 20:33 ` tglx
2018-10-29 20:33 ` Thomas Gleixner
2018-10-29 21:21 ` ebiederm
2018-10-29 21:21 ` Eric W. Biederman
2018-10-29 21:36 ` tglx
2018-10-29 21:36 ` Thomas Gleixner
2018-10-31 16:26 ` avagin
2018-10-31 16:26 ` Andrei Vagin
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='CAJwJo6bseG42YNqA0cxWpB0C252_CWER0gDrF0OUOm+=DJ7XdQ@mail.gmail.com' \
--to=linux-kselftest@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).