From: "Flávio Silveira" <fggs@terra.com.br>
To: netdev@vger.kernel.org, Chris Snook <chris.snook@gmail.com>,
jcliburn@gmail.com
Subject: Re: Attansic L1 driver issue
Date: Tue, 12 Jan 2016 13:13:03 -0200 [thread overview]
Message-ID: <569517FF.6060602@terra.com.br> (raw)
In-Reply-To: <56876713.9090100@terra.com.br>
On 02/01/2016 03:58, Flávio Silveira wrote:
> Good morning,
>
> I'm investigating a possible issue with atl1 driver used by Attansic
> L1.
>
> During my tests with iperf3 I saw a performance drop when the
> computer is client.
>
> I can hit only about 580~600Mbit/s, if I disable
> generic-segmentation-offload (GSO) I can hit 660~670Mbit/s.
>
> When the computer is server, I can hit 940~950Mbit/s.
Hi,
I'm continuing to investigate this, tried older kernels (2.6.32 and
3.2.68) in order to see if it was a regression.
What I discovered so far is that if I disable scatter-gather I can
see around 70Mbit/s of improvement, I wonder if there is anything else I
can do to understand the "tx busy" message I mentioned in first mail or
the issue itself.
Regards,
Flavio
prev parent reply other threads:[~2016-01-12 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 5:58 Attansic L1 driver issue Flávio Silveira
2016-01-12 15:13 ` Flávio Silveira [this message]
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=569517FF.6060602@terra.com.br \
--to=fggs@terra.com.br \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.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 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.