[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78C9135A3D2ECE4B8162EBDCE82CAD77051BEB23@nekter>
Date: Fri, 27 Mar 2009 19:09:24 -0400
From: "Ramkrishna Vepa" <Ramkrishna.Vepa@...erion.com>
To: "David Miller" <davem@...emloft.net>
Cc: <netdev@...r.kernel.org>
Subject: RE: [net-2.6 PATCH 1/9] Neterion: Driver help file
> I'm not apply any of this patch set.
>
> > +4) Performance Suggestions:
> > +---------------------------
> > +
> > +- Set MTU to maximum - 9000 for switch setup, 9600 for
back-to-back.
> > +For MTU 1500:
> > +-------------
> > +### IPV4 specific settings
> > +# turns TCP timestamp support off, default 1, reduces CPU use
> > +$sysctl -w net.ipv4.tcp_timestamps = "0"
>
> You have got to be kidding me.
>
> I see this garbage in the "tuning suggestions" sections of
> various manuals of proprietary products for Linux.
>
> But there is no way I'm letting this junk slip into Linux proper too.
>
> All of these suggestions are ill founded, have side effects that are
> not even passively mentioned in these "suggestions", and are even
> dangerous.
>
> Do you even know the security implications of turning off TCP
timestamps?
> Do you know or even feel the need to mention the performance
implications
> over long haul networks of turning timestamps off?
[Ram] I should have removed this suggestion. We usually suggest that
timestamps (and SACKs) be left enabled. We'll remove this section. Is it
ok I resend just this patch instead of the whole series?
>
> If the default sysctl parameters are not correct, let's fix them
instead
> of telling every user how to break their system with "tweaks".
[Ram] I'll send some suggestions for the sysctl parameters in a separate
thread.
Ram
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists