From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: netdev@vger.kernel.org
Subject: Re: packetloss, on e1000e worse than r8169?
Date: Tue, 17 Jun 2008 01:08:41 +0300 [thread overview]
Message-ID: <20080616220841.M50112@visp.net.lb> (raw)
In-Reply-To: <4856DEA7.9060506@cosmosbay.com>
On Mon, 16 Jun 2008 23:44:07 +0200, Eric Dumazet wrote
>
> ALso please try to lower the copybreak value of e1000e driver
> (module parameter copybreak=20 for example)
Already tried, but over sysfs
MegaRouter-KARAM ~ # echo 20 > /sys/module/e1000e/parameters/copybreak
Doesn't change anything. I am preparing profiling now.
I dont think it is CPU load issue. I have motherboard DP35DP working on
similar workload(less routes, but conntrack + ifb + htb without hysteresis)
perfectly, but it doesn't have Intel AMT, maybe that's the key.
Why CPU load not the issue? I don't think mpstat is lying. 98-99% CPU is idle.
But i will try oprofile, maybe it can help and will show something.
I will try also PREEMPT kernel now, maybe it is some locking issue, and
preemption can help with that. Because "bursty" and clearly periodic character
of errors means or counters updated each 1-2 seconds or it is something
happening each 1-2 seconds. I am not sure oprofile can catch that.
MegaRouter-KARAM ~ # mpstat 1
Linux 2.6.26-rc6-git2-build-0029 (MegaRouter-KARAM) 06/17/08
00:54:23 CPU %user %nice %sys %iowait %irq %soft %steal
%idle intr/s
00:54:24 all 0.51 0.00 0.00 0.00 0.00 1.02 0.00
98.48 18902.00
00:54:25 all 0.00 0.00 0.00 0.00 0.00 0.51 0.00
99.49 18735.00
00:54:26 all 0.00 0.00 0.00 0.00 0.00 0.48 0.00
99.52 19057.00
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next prev parent reply other threads:[~2008-06-16 22:12 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
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 [this message]
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=20080616220841.M50112@visp.net.lb \
--to=denys@visp.net.lb \
--cc=dada1@cosmosbay.com \
--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).