On Thu, Sep 01, 2005 at 01:50:33AM +0200, Roman Zippel wrote:
> When you convert a user time to kernel time you can
> automatically validate
Kernel time sucks. It is just a single clock, it may not have
the attributes of the clock that the user really wished to use.
Joe
Hi,
On Thu, 1 Sep 2005, Joe Korty wrote:
> > When you convert a user time to kernel time you can
> > automatically validate
>
> Kernel time sucks. It is just a single clock, it may not have
> the attributes of the clock that the user really wished to use.
Wrong. The kernel time is simple and effective for almost all users.
We are talking about _timeouts_ here, what fancy "attributes" does that
need that are just not overkill?
bye, Roman
On Thu, 2005-09-01 at 16:32 +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 1 Sep 2005, Joe Korty wrote:
>
> > > When you convert a user time to kernel time you can
> > > automatically validate
> >
> > Kernel time sucks. It is just a single clock, it may not have
> > the attributes of the clock that the user really wished to use.
>
> Wrong. The kernel time is simple and effective for almost all users.
> We are talking about _timeouts_ here, what fancy "attributes" does that
> need that are just not overkill?
Or rather, posix timers ?
Daniel
On Thu, 2005-09-01 at 16:32 +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 1 Sep 2005, Joe Korty wrote:
>
> > > When you convert a user time to kernel time you can
> > > automatically validate
> >
> > Kernel time sucks. It is just a single clock, it may not have
> > the attributes of the clock that the user really wished to use.
>
> Wrong. The kernel time is simple and effective for almost all users.
> We are talking about _timeouts_ here, what fancy "attributes" does that
> need that are just not overkill?
How do you feel about posix clocks ?
Daniel
On Thu, Sep 01, 2005 at 04:32:49PM +0200, Roman Zippel wrote:
> On Thu, 1 Sep 2005, Joe Korty wrote:
> > Kernel time sucks. It is just a single clock, it may not have
> > the attributes of the clock that the user really wished to use.
>
> Wrong. The kernel time is simple and effective for almost all users.
> We are talking about _timeouts_ here, what fancy "attributes" does that
> need that are just not overkill?
The name should be changed from 'struct timeout' to something like
'struct timeevent'.
Joe