From: Joao Pinto <Joao.Pinto@synopsys.com>
To: davem@davemloft.net, clabbe.montjoie@gmail.com,
treding@nvidia.com, niklas.cassel@axis.com
Cc: netdev@vger.kernel.org, Joao Pinto <Joao.Pinto@synopsys.com>
Subject: [PATCH 0/4 v2 net-next] net: stmmac: adding multiple buffers
Date: Wed, 5 Apr 2017 17:43:00 +0100 [thread overview]
Message-ID: <cover.1491409859.git.jpinto@synopsys.com> (raw)
This patch adds multiple buffers to stmmac in a more fragmented
way, in order to make problem debug easier.
I would kindly request to people to test this patch in their HWs in
order to check if everything's functional. Thank you.
Joao Pinto (4):
net: stmmac: break some functions into RX and TX scopes
net: stmmac: adding multiple buffers for RX
net: stmmac: adding multiple buffers for TX
net: stmmac: adding multiple napi mechanism
drivers/net/ethernet/stmicro/stmmac/chain_mode.c | 45 +-
drivers/net/ethernet/stmicro/stmmac/ring_mode.c | 46 +-
drivers/net/ethernet/stmicro/stmmac/stmmac.h | 49 +-
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 1257 ++++++++++++++-------
4 files changed, 947 insertions(+), 450 deletions(-)
--
2.9.3
next reply other threads:[~2017-04-05 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 16:43 Joao Pinto [this message]
2017-04-05 16:43 ` [PATCH 1/4 v2 net-next] net: stmmac: break some functions into RX and TX scopes Joao Pinto
2017-04-05 16:43 ` [PATCH 2/4 v2 net-next] net: stmmac: adding multiple buffers for RX Joao Pinto
2017-04-05 16:43 ` [PATCH 3/4 v2 net-next] net: stmmac: adding multiple buffers for TX Joao Pinto
2017-04-05 16:43 ` [PATCH 4/4 v2 net-next] net: stmmac: adding multiple napi mechanism Joao Pinto
2017-04-05 16:59 ` [PATCH 0/4 v2 net-next] net: stmmac: adding multiple buffers Corentin Labbe
2017-04-06 8:24 ` Joao Pinto
2017-04-07 9:20 ` Corentin Labbe
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=cover.1491409859.git.jpinto@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=niklas.cassel@axis.com \
--cc=treding@nvidia.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).