On Tue, Mar 06, 2007 at 04:16:24PM +0100, Eric Dumazet wrote:
>
> It would be better to name the tunable "disable_timestamps", default 0 of
> course
I agree.
If networking maintainers are interested, I surely can prepare a patch.
But IMO some way to force TSC usage on x86_64 will be even b
On Tuesday 06 March 2007 15:43, Vladimir B. Savkin wrote:
> On Tue, Mar 06, 2007 at 03:38:44PM +0100, Eric Dumazet wrote:
> > 2) "accurate_timestamps" is misleading.
> > Should be "disable_timestamps"
>
> Not, if default is 1, as in my patch.
Yes I saw this. I should write more words next time
On Tue, Mar 06, 2007 at 03:38:44PM +0100, Eric Dumazet wrote:
> 2) "accurate_timestamps" is misleading.
> Should be "disable_timestamps"
Not, if default is 1, as in my patch.
~
:wq
With best regards,
Vladi
On Tuesday 06 March 2007 14:25, Vladimir B. Savkin wrote:
> },
> + {
> + .ctl_name = NET_CORE_ACCURATE_TIMESTAMPS,
> + .procname = "accurate_timestamps",
> + .data = &sysctl_accurate_timestamps,
> + .maxlen = s
On Fri, Sep 22, 2006 at 09:51:09AM -0700, Rick Jones wrote:
> >That came from named. It opens lots of sockets with SIOCGSTAMP.
> >No idea what it needs that many for.
>
> IIRC ISC BIND named opens a socket for each IP it finds on the system.
> Presumeably in this way it "knows" implicitly the des
5 matches
Mail list logo
