Mark Atwood :
> Go has a GC. the Go standard library and the complier implementation will
> always be utterly controlled by Google, and will be full of Google magic.
> Go's usecase is to solve Google's problems, and can basically be modelled
> as "compiled Python that
Go has a GC. the Go standard library and the complier implementation will
always be utterly controlled by Google, and will be full of Google magic.
Go's usecase is to solve Google's problems, and can basically be modelled
as "compiled Python that forcefully avoids all of the kinds of typos that
Dr
Dan Drown :
> Quoting "Eric S. Raymond" :
> >Achim Gratz :
> >>…or move the refclocks out of ntpd altogether and use some shared memory
> >>or mailbox system to have ntpd have a look at the timestamp stream from
> >>each refclock.
> >
>
Quoting "Eric S. Raymond" :
Achim Gratz :
…or move the refclocks out of ntpd altogether and use some shared memory
or mailbox system to have ntpd have a look at the timestamp stream from
each refclock.
Yeah, this is one of my longer-term plans. It was in
Yo Eric!
On Wed, 14 Sep 2016 17:22:51 -0400
"Eric S. Raymond" wrote:
> Gary E. Miller :
> > Sadly, unless you have threading there is no way to A/B test it
> > against no threading. So let us not rip out any existing threading
> > until it gets tested.
>
>
Gary E. Miller :
> Sadly, unless you have threading there is no way to A/B test it against
> no threading. So let us not rip out any existing threading until it
> gets tested.
There isn't threading any there to rip out, except for the one hack to avoid
stalls on DNS lookups.
Yo Eric!
On Wed, 14 Sep 2016 16:41:47 -0400
"Eric S. Raymond" wrote:
> Eric S. Raymond :
> > John D. Bell :
> > > *If* I were the architect on this project (thankfully I'm not!) I
> > > would get the code simplified and streamlined
Eric S. Raymond :
> John D. Bell :
> > *If* I were the architect on this project (thankfully I'm not!) I
> > would get the code simplified and streamlined in single-thread mode
> > as far as possible, and then design and code a
> >
Eric S. Raymond writes:
> Hal:
>
> But maybe we should have a separate thread per refclock to get the
> time stamp. ...
…or move the refclocks out of ntpd altogether and use some shared memory
or mailbox system to have ntpd have a look at the timestamp stream from
each refclock. Then you have
Current professional systems administrator (former professional programmer)
here. I hope I am adding light and not merely heat to this discussion.
quoting Eric -
> The underlying point is that blade and rack servers are cheap. Cycles
> are cheap. This gives the option of implicitly saying to
10 matches
Mail list logo