From: Jan Engelhardt <jengelh@inai.de>
To: Prashant Batra <prashant0100@gmail.com>
Cc: "linux-newbie@vger.kernel.org" <linux-newbie@vger.kernel.org>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: IPv6 routes too much
Date: Sat, 9 Feb 2013 04:31:42 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.01.1302090428001.25836@nerf07.vanv.qr> (raw)
In-Reply-To: <CAG+XuE5g9jJTP4uu5ymQfzvx-O6U9SfK85XGoK+H7yqtVA6A0A@mail.gmail.com>
On Friday 2013-02-08 18:33, Prashant Batra wrote:
>
>So, any advice onto how the kernel configs specially under
>/proc/sys/net/ipv6/route/* should be controlled to get best performance.
The defaults should be good enough.
If they are not: Measure it.
prev parent reply other threads:[~2013-02-09 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 10:48 IPv6 routes too much Prashant Batra
2013-02-08 15:34 ` Jan Engelhardt
2013-02-08 17:38 ` Prashant Batra
[not found] ` <CAG+XuE5g9jJTP4uu5ymQfzvx-O6U9SfK85XGoK+H7yqtVA6A0A@mail.gmail.com>
2013-02-09 3:31 ` Jan Engelhardt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.01.1302090428001.25836@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=linux-newbie@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=prashant0100@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).