From: Eric Dumazet <dada1@cosmosbay.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: packetloss, on e1000e worse than r8169?
Date: Mon, 16 Jun 2008 23:29:01 +0200 [thread overview]
Message-ID: <4856DB1D.80503@cosmosbay.com> (raw)
In-Reply-To: <20080616211213.M76390@visp.net.lb>
Denys Fedoryshchenko a écrit :
>> Are you sure nf_conntrack or ip route cache is not killing you ?
>>
>> Filling 512 or 1024 RX ring on Gigabit link can be very fast, especially
>> if ip route cache is full.
>>
>> rtstat -c10 -i1
>
> conntrack disabled, it is just enabled for second on load and then unloaded.
ok :)
>
> MegaRouter-KARAM ~ # rtstat -c10 -i1
> rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|rt_cache|
> entries| in_hit|in_slow_|in_slow_|in_no_ro| in_brd|in_marti|in_marti|
> out_hit|out_slow|out_slow|gc_total|gc_ignor|gc_goal_|gc_dst_o|in_hlist|out_hlis|
> | | tot| mc| ute| | an_dst| an_src|
> | _tot| _mc| | ed| miss| verflow| _search|t_search|
> 63448|229209146|22225578| 13754| 12| 2822| 0| 104|
> 54647| 27606| 570|21782075|21776859| 74| 0|215222374| 61294|
> 66085| 141462| 5268| 8| 0| 4| 0| 0|
> 4| 2| 0| 5274| 5274| 0| 0| 254424| 10|
> 59947| 132660| 20570| 4| 0| 4| 0| 0|
> 8| 14| 0| 20584| 20584| 0| 0| 185738| 24|
> 56995| 132416| 16918| 12| 0| 2| 0| 0|
> 6| 4| 0| 16932| 16932| 0| 0| 68378| 8|
> 56422| 137058| 12336| 8| 0| 0| 0| 0|
> 8| 2| 0| 12344| 12344| 0| 0| 84022| 4|
> 56819| 140526| 9896| 10| 0| 0| 0| 0|
> 6| 0| 0| 9898| 9896| 0| 0| 99138| 4|
> 57580| 136936| 8370| 10| 0| 2| 0| 0|
> 8| 6| 2| 8378| 8378| 0| 0| 110834| 22|
> 51583| 120138| 26828| 20| 0| 0| 0| 0|
> 4| 8| 0| 26848| 26848| 0| 0| 99292| 24|
> 49354| 128076| 21606| 14| 0| 2| 0| 0|
> 0| 10| 0| 21626| 21626| 0| 0| 60546| 12|
>
>
>
Hum... typical IP route cache congestion ?
echo 1 >/proc/sys/net/ipv4/route/gc_interval
echo 2 >/proc/sys/net/ipv4/route/gc_elasticity
You might want to boot with rhash_entries=131071 to play with IP route cache size, but I am not sure your workload can fit.
next prev parent reply other threads:[~2008-06-16 21:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 19:37 packetloss, on e1000e worse than r8169? Denys Fedoryshchenko
2008-06-16 19:48 ` Eric Dumazet
2008-06-16 20:20 ` Denys Fedoryshchenko
2008-06-16 20:23 ` Denys Fedoryshchenko
2008-06-16 20:36 ` Kok, Auke
2008-06-16 20:52 ` Denys Fedoryshchenko
[not found] ` <20080616204411.M52834@visp.net.lb>
2008-06-16 20:49 ` Kok, Auke
2008-06-16 20:59 ` Denys Fedoryshchenko
2008-06-16 21:13 ` Denys Fedoryshchenko
2008-06-16 21:29 ` Eric Dumazet [this message]
2008-06-16 21:41 ` Denys Fedoryshchenko
2008-06-16 21:41 ` Denys Fedoryshchenko
[not found] ` <20080616213419.M212@visp.net.lb>
2008-06-16 21:41 ` Eric Dumazet
2008-06-16 21:44 ` Eric Dumazet
2008-06-16 22:08 ` Denys Fedoryshchenko
2008-06-17 2:17 ` Eric Dumazet
2008-06-17 2:47 ` Denys Fedoryshchenko
2008-06-16 22:08 ` Denys Fedoryshchenko
2008-06-16 23:24 ` Brandeburg, Jesse
2008-06-17 1:53 ` Denys Fedoryshchenko
2008-06-17 6:46 ` Denys Fedoryshchenko
2008-06-17 17:22 ` Denys Fedoryshchenko
2008-06-18 0:58 ` Brandeburg, Jesse
2008-06-17 21:04 ` Denys Fedoryshchenko
2008-06-18 16:50 ` Brandeburg, Jesse
2008-06-18 17:03 ` Denys Fedoryshchenko
2008-06-16 21:17 ` Denys Fedoryshchenko
2008-06-16 21:05 ` Eric Dumazet
2008-06-16 20:15 ` Auke Kok
2008-06-16 20:29 ` Denys Fedoryshchenko
2008-06-16 20:26 ` Francois Romieu
2008-06-16 20:37 ` Waskiewicz Jr, Peter P
2008-06-16 20:42 ` Denys Fedoryshchenko
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=4856DB1D.80503@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=denys@visp.net.lb \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.