From: clabbe.montjoie@gmail.com (Corentin Labbe)
To: linux-arm-kernel@lists.infradead.org
Subject: stmmac: Performance regression after commit aff3d9eff843 "net: stmmac: enable multiple buffers"
Date: Thu, 23 Mar 2017 11:08:28 +0100 [thread overview]
Message-ID: <20170323100828.GC16625@Red> (raw)
Hello
Using next-20170323 produce a huge performance regression on my sunxi boards.
On dwmac-sun8i, iperf goes from 94mbs/s to 37 when sending.
On cubieboard2(dwmac-sunxi), iperf made the kernel flood with "ndesc_get_rx_status: Oversized frame spanned multiple buffers"
and network is lost after.
Reverting aff3d9eff84399e433c4aca65a9bb236581bc082 fix the issue.
I still try to found which part of this patch mades the performance lower.
Regards
Corentin Labbe
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Joao.Pinto@synopsys.com, peppe.cavallaro@st.com, alexandre.torgue@st.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: stmmac: Performance regression after commit aff3d9eff843 "net: stmmac: enable multiple buffers"
Date: Thu, 23 Mar 2017 11:08:28 +0100 [thread overview]
Message-ID: <20170323100828.GC16625@Red> (raw)
Hello
Using next-20170323 produce a huge performance regression on my sunxi boards.
On dwmac-sun8i, iperf goes from 94mbs/s to 37 when sending.
On cubieboard2(dwmac-sunxi), iperf made the kernel flood with "ndesc_get_rx_status: Oversized frame spanned multiple buffers"
and network is lost after.
Reverting aff3d9eff84399e433c4aca65a9bb236581bc082 fix the issue.
I still try to found which part of this patch mades the performance lower.
Regards
Corentin Labbe
next reply other threads:[~2017-03-23 10:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 10:08 Corentin Labbe [this message]
2017-03-23 10:08 ` stmmac: Performance regression after commit aff3d9eff843 "net: stmmac: enable multiple buffers" Corentin Labbe
2017-03-23 10:12 ` Joao Pinto
2017-03-23 10:12 ` Joao Pinto
2017-03-23 10:20 ` Corentin Labbe
2017-03-23 10:20 ` Corentin Labbe
2017-03-23 10:40 ` Joao Pinto
2017-03-23 10:40 ` Joao Pinto
2017-03-23 10:48 ` Giuseppe CAVALLARO
2017-03-23 10:48 ` Giuseppe CAVALLARO
2017-03-23 10:48 ` Giuseppe CAVALLARO
2017-03-23 10:51 ` Giuseppe CAVALLARO
2017-03-23 10:51 ` Giuseppe CAVALLARO
2017-03-23 10:51 ` Giuseppe CAVALLARO
2017-03-23 10:56 ` Joao Pinto
2017-03-23 10:56 ` Joao Pinto
2017-03-23 12:55 ` Joao Pinto
2017-03-23 12:55 ` Joao Pinto
2017-03-23 10:54 ` Joao Pinto
2017-03-23 10:54 ` Joao Pinto
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=20170323100828.GC16625@Red \
--to=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.