lkml.org 
[lkml]   [2006]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Network performance degradation from 2.6.11.12 to 2.6.16.20
    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.

    Alexey
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-09-19 00:03    [W:4.186 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site