From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Joao Pinto <Joao.Pinto@synopsys.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: <alexandre.torgue@st.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: stmmac: Performance regression after commit aff3d9eff843 "net: stmmac: enable multiple buffers"
Date: Thu, 23 Mar 2017 11:48:38 +0100 [thread overview]
Message-ID: <465dc72e-8a1f-b41f-105f-add2164df6d5@st.com> (raw)
In-Reply-To: <a7c928ec-e4e5-b618-d0d4-2a833be10d53@synopsys.com>
Hello
On 3/23/2017 11:20 AM, Corentin Labbe wrote:
>> I have a 4.21 QoS Core with 4 RX + 4 TX and detected no regression.
>> >Could you please share the iperf cmds you are using in order for me to reproduce
>> >in my side?
Joao, you have a really powerful HW integration with multiple channels
for both RX and TX.
Often this is not the same for other setup where, usually just a DMA0 is
present or, sometime, there
is just one RX extra channel.
My question is, what happens on this kind of configurations? Are we
still guarantying the best performances?
Also we have to guarantee, that the TSO and SG are always working.
Another point is the buffer sizes that
can be different among platforms.
The problem below reported by Corentin push me to think that there is a
bug, so we should
understand when this has been introduced and if likely fixed by some
configuration we are
not take care right now.
ndesc_get_rx_status: Oversized frame spanned multiple buffers"
Best Regards
Peppe
next prev parent reply other threads:[~2017-03-23 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 10:08 Corentin Labbe
2017-03-23 10:12 ` Joao Pinto
2017-03-23 10:20 ` Corentin Labbe
2017-03-23 10:40 ` Joao Pinto
2017-03-23 10:48 ` Giuseppe CAVALLARO [this message]
2017-03-23 10:51 ` Giuseppe CAVALLARO
2017-03-23 10:56 ` Joao Pinto
2017-03-23 12:55 ` 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=465dc72e-8a1f-b41f-105f-add2164df6d5@st.com \
--to=peppe.cavallaro@st.com \
--cc=Joao.Pinto@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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
all inboxes | Powered by JetHome®