netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arun Sharma <asharma@fb.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: compute a more reasonable default ip6_rt_max_size
Date: Sat, 26 May 2012 20:54:34 -0700	[thread overview]
Message-ID: <4FC1A57A.7080807@fb.com> (raw)
In-Reply-To: <1338003580.10135.6.camel@edumazet-glaptop>

On 5/25/12 8:39 PM, Eric Dumazet wrote:
>
> But your patch is not a  "modest increase", so whats the deal ?
>
> A modest increase would be 8192 instead of 4096, regardless of RAM size.
>

Yes - 8192 solves our immediate problem, but I was worrying that the 
problem might resurface as ipv6 adoption becomes more widespread.

We were testing a pre-3.0 kernel that didn't have Dave's DST_NOCOUNT 
patch. Will retest with that patch applied.

 > More over, a boot parameter to tweak it is absolutely not needed

Agreed. Will remove that part.

Still not sure why you'd like to go for one size regardless of 
totalram_pages.

  -Arun

  parent reply	other threads:[~2012-05-27  3:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 20:15 [PATCH] net: compute a more reasonable default ip6_rt_max_size Arun Sharma
2012-05-25 20:26 ` David Miller
2012-05-25 20:47 ` Eric Dumazet
2012-05-25 22:22   ` Arun Sharma
2012-05-25 22:51     ` David Miller
2012-05-26  0:08       ` Arun Sharma
2012-05-26  0:11         ` David Miller
2012-05-26  0:44           ` Arun Sharma
2012-05-26  3:39             ` Eric Dumazet
2012-05-26  4:17               ` Eric Dumazet
2012-05-27  3:54               ` Arun Sharma [this message]
2012-05-27 13:18                 ` Eric Dumazet
  -- strict thread matches above, loose matches on Subject: below --
2012-05-30 23:50 Lubashev, Igor
2012-06-04 19:04 ` Lubashev, Igor

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=4FC1A57A.7080807@fb.com \
    --to=asharma@fb.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 NNTP newsgroup(s).