Re: Network performance degradation from 2.6.11.12 to 2.6.16.20

David Lang
2006-09-18T22:09:34Z

On Tue, 19 Sep 2006, Alexey Kuznetsov wrote:

> Hello!
>
>> Please think about it this way:
>> suppose you haave a heavily loaded router and some network problem is to
>> be diagnosed. You run tcpdump and suddenly router becomes overloaded (by
>> switching to timestamp-it-all mode
>
> I am sorry. I cannot think that way. :-)
>
> Instead of attempts to scare, better resend original report,
> where you said how much performance degraded, I cannot find it.
>
> * I do see get_offset_pmtmr() in top lines of profile. That's scary enough.
> * I do not undestand what the hell dhcp needs timestamps for.
> * I do not listen any suggestions to screw up tcpdump with a sysctl.
> Kernel already implements much better thing then a sysctl.
> Do not want timestamps? Fix tcpdump, add an options, submit the
> patch to tcpdump maintainers. Not a big deal.

if fireing up one program (however minor) can cause network performance to drop
by >50% (based on the numbers reported earlier in this thread) that is a
significant problem for sysadmins.

yes tcpdump may be wrong in requesting timestamps (in most cases it probably is,
but in some cases it's doing exactly what the sysadmin wants it to do), but I
don't think that many sysadmins would expect this much of a performance hit.
there should be some way to tell the system to ignore requests for timestamps so
that a badly behaved program cannot cripple the system this way (and preferably
something that doesn't require a full SELinux/capabilities implementation)

David Lang