[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vDSO? (was: [SCM] Web pages branch, master, updated. 357bc0213f1d40

From: Samuel Thibault
Subject: Re: vDSO? (was: [SCM] Web pages branch, master, updated. 357bc0213f1d4049d6ce0c80122987c760c5e506)
Date: Wed, 10 Apr 2013 01:17:20 +0200
User-agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30)

Thomas Schwinge, le Sun 07 Apr 2013 01:21:51 +0200, a écrit :
> | Having vDSO code might be useful for:
> | 
> |   * `mach_*_self`: `mach_host_self`, `mach_task_self`, `mach_thread_self`?

Mmm, but these are supposed to add a reference count on the send right.

> |   * 
> [[mapped-time_interface|master/microkernel/mach/gnumach/interface/device/time]]
> | 
> |     Every application can then use that via the regular
> |     `gettimeofday`/`clock_gettime` and similar calls instead of using the
> |     special [[hurd/libshouldbeinlibc]]'s `<maptime.h>` interface.
> | 
> |     Can implement [[`clock_gettime` stuff|clock_gettime]] more easily that 
> way,
> |     for example for nanosecond precision?

Oh, I thought gettimeofday was already using the mapped time, but
apparently not. It would definitely be useful to avoid a syscall here.

> |     Now, the [[mapped-time_interface]] is virtualizable -- the question is
> |     whether there is a way so that we can make a compromise here?

I don't see what problem you are seeing here. glibc would mmap
/dev/time, which can be interposed, that's all fine.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]