From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Jeff Dike <jdike-OPE4K8JWMJJBDgjK7y7TUQ@public.gmane.org>
Subject: Re: c/r, time, and virtualization
Date: Sat, 25 Jul 2009 00:26:50 -0700 [thread overview]
Message-ID: <m1y6qdkyth.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4A6A93FC.7090209-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org> (Oren Laadan's message of "Sat\, 25 Jul 2009 01\:11\:24 -0400")
Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org> writes:
> Hi,
>
> I wonder what's that status of time namespaces and virtual time(rs) ?
>
> http://lwn.net/Articles/180375/ - "virtual time" coverage in LWN (2006)
> http://lkml.org/lkml/2006/4/13/172 - patchset and thread on LKML
> http://lwn.net/Articles/249080/ - kernel summit 2007 - containers
>
> It will be handy for c/r of timers (posix-timers) that I'm working on.
>
> A couple of obstacles off the top of my head:
>
> - Lack of clone flags -- we can use clone_with_pids() for that.
>
> - Fast gettimeofday() via vdso -- perhaps a vdso page per time-ns
> (containing the necessary deltas).
>
> Is anyone working on it ?
I proposed it, for the reason you care.
I have thought about the semantics.
But I haven't gotten as far as implementing something.
I will be happy to bounce ideas off, and review code
when I have a few seconds free.
Eric
prev parent reply other threads:[~2009-07-25 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 5:11 c/r, time, and virtualization Oren Laadan
[not found] ` <4A6A93FC.7090209-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-07-25 7:26 ` Eric W. Biederman [this message]
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=m1y6qdkyth.fsf@fess.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=jdike-OPE4K8JWMJJBDgjK7y7TUQ@public.gmane.org \
--cc=orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.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