From: David Miller <davem@davemloft.net>
To: john@phrozen.org
Cc: sean.wang@mediatek.com, linux-mediatek@lists.infradead.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] net-next: mediatek: various performance improvements
Date: Tue, 20 Jun 2017 13:40:52 -0400 (EDT) [thread overview]
Message-ID: <20170620.134052.264394808259657804.davem@davemloft.net> (raw)
In-Reply-To: <20170619133706.3415-1-john@phrozen.org>
From: John Crispin <john@phrozen.org>
Date: Mon, 19 Jun 2017 15:37:02 +0200
> During development we mainly ran testing using iperf doing 1500 byte
> tcp frames. It was pointed out recently, that the driver does not perform
> very well when using 512 byte udp frames. The biggest problem was that
> RPS was not working as no rx queue was being set. fixing this more than
> doubled the throughput. Additionally the IRQ mask register is now locked
> independently for RX and TX. RX IRQ aggregation is also added. With all
> these patches applied we can almost triple the throughput.
>
> While at it we also add PHY status change reporting for GMACs connecting
> directly to a PHY.
Series applied, thank you.
prev parent reply other threads:[~2017-06-20 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 13:37 [PATCH 0/4] net-next: mediatek: various performance improvements John Crispin
2017-06-19 13:37 ` [PATCH 1/4] net-next: mediatek: print phy status changes for non DSA GMACs John Crispin
2017-06-19 13:37 ` [PATCH 2/4] net-next: mediatek: add RX IRQ delay support John Crispin
2017-06-19 13:37 ` [PATCH 3/4] net-next: mediatek: split IRQ register locking into TX and RX John Crispin
2017-06-19 13:37 ` [PATCH 4/4] net-next: mediatek: set the rx_queue to 0 John Crispin
2017-06-20 17:40 ` David Miller [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=20170620.134052.264394808259657804.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=john@phrozen.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
/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).