From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Paweł Staszewski" <pstaszewski@itcare.pl>
Cc: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: Linux Route Cache performance tests
Date: Mon, 07 Nov 2011 00:08:35 +0100 [thread overview]
Message-ID: <1320620915.6506.44.camel@edumazet-laptop> (raw)
In-Reply-To: <4EB702D3.1090703@itcare.pl>
Le dimanche 06 novembre 2011 à 22:57 +0100, Paweł Staszewski a écrit :
> W dniu 2011-11-06 22:26, Eric Dumazet pisze:
> > Le dimanche 06 novembre 2011 à 21:25 +0100, Paweł Staszewski a écrit :
> >> Yes with this is a little problem i think with kernel 3.1 because
> >> dmesg | egrep '(rhash)|(route)'
> >> [ 0.000000] Command line: root=/dev/md2 rhash_entries=2097152
> >> [ 0.000000] Kernel command line: root=/dev/md2 rhash_entries=2097152
> >> [ 4.697294] IP route cache hash table entries: 524288 (order: 10,
> >> 4194304 bytes)
> >>
> >>
> > Dont tell me you _still_ use a 32bit kernel ?
> no it is 64bit :)
> Linux localhost 3.1.0 #16 SMP Sun Nov 6 18:09:48 CET 2011 x86_64 Intel(R)
> :)
>
> > If so, you need to tweak alloc_large_system_hash() to use vmalloc,
> > because you hit MAX_ORDER (10) page allocations.
> funny then :)
> Maybee i turned off too many kernel features
> > But considering LOWMEM is about 700 Mbytes, you wont be able to create a
> > lot of route cache entries.
> >
> > Come on, do us a favor, and enter new era of computing.
OK, then your kernel is not CONFIG_NUMA enabled
It seems strange given you probably have a NUMA machine (24 cpus)
If so, your choices are :
1) enable CONFIG_NUMA. Really this is a must given the workload of your
machine.
2) Or : you need to add "hashdist=1" on boot params
and patch your kernel with following patch :
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 9dd443d..07f86e0 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -5362,7 +5362,6 @@ int percpu_pagelist_fraction_sysctl_handler(ctl_table *table, int write,
int hashdist = HASHDIST_DEFAULT;
-#ifdef CONFIG_NUMA
static int __init set_hashdist(char *str)
{
if (!str)
@@ -5371,7 +5370,6 @@ static int __init set_hashdist(char *str)
return 1;
}
__setup("hashdist=", set_hashdist);
-#endif
/*
* allocate a large system hash table from bootmem
next prev parent reply other threads:[~2011-11-06 23:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 15:57 Linux Route Cache performance tests Paweł Staszewski
2011-11-06 17:29 ` Eric Dumazet
2011-11-06 18:28 ` Paweł Staszewski
2011-11-06 18:48 ` Eric Dumazet
2011-11-06 19:20 ` Paweł Staszewski
2011-11-06 19:38 ` Eric Dumazet
2011-11-06 20:25 ` Paweł Staszewski
2011-11-06 21:26 ` Eric Dumazet
2011-11-06 21:57 ` Paweł Staszewski
2011-11-06 23:08 ` Eric Dumazet [this message]
2011-11-07 8:36 ` Paweł Staszewski
2011-11-07 9:08 ` Eric Dumazet
2011-11-07 9:16 ` Eric Dumazet
2011-11-07 22:12 ` Paweł Staszewski
2011-11-07 13:42 ` Ben Hutchings
2011-11-07 14:33 ` Eric Dumazet
2011-11-09 17:24 ` [PATCH net-next] ipv4: PKTINFO doesnt need dst reference Eric Dumazet
2011-11-09 21:37 ` David Miller
2011-11-09 22:03 ` Eric Dumazet
2011-11-10 0:29 ` [PATCH net-next] bnx2x: reduce skb truesize by 50% Eric Dumazet
2011-11-10 15:05 ` Eilon Greenstein
2011-11-10 15:27 ` Eric Dumazet
2011-11-10 16:27 ` Eilon Greenstein
2011-11-10 16:45 ` Eric Dumazet
2011-11-13 18:53 ` Eilon Greenstein
2011-11-13 19:42 ` Eric Dumazet
2011-11-13 20:08 ` Eilon Greenstein
2011-11-13 22:00 ` Eric Dumazet
2011-11-14 5:08 ` David Miller
2011-11-14 6:25 ` Eric Dumazet
2011-11-14 15:57 ` Eric Dumazet
2011-11-14 19:21 ` David Miller
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=1320620915.6506.44.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
/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