netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcin Wojtas <mw@semihalf.com>
To: linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Cc: davem@davemloft.net, jason@lakedaemon.net,
	thomas.petazzoni@free-electrons.com,
	gregory.clement@free-electrons.com,
	ezequiel.garcia@free-electrons.com, alior@marvell.com,
	jaz@semihalf.com, Marcin Wojtas <mw@semihalf.com>
Subject: [PATCH 0/3] Fixes for the network driver of Marvell Armada 375 SoC
Date: Thu,  6 Aug 2015 19:00:27 +0200	[thread overview]
Message-ID: <1438880430-5480-1-git-send-email-mw@semihalf.com> (raw)
In-Reply-To: <y>

Hello,

This is a set of three patches that fix long-lasting problems implemented in
the initial support for the Armada 375 network controller.

Due to an inappropriate concept of handling the per-CPU sent packets'
processing on TX path the driver numerous problems occured, such as RCU
stalls. Those have been fixed, of which details you can find in the commit
logs. The patches were intensively tested on top of v4.2-rc5.

I'm looking forward to any comments or remarks.

Thanks,
Marcin

Marcin Wojtas (3):
  net: mvpp2: remove excessive spinlocks from driver initialization
  net: mvpp2: enable proper per-CPU TX buffers unmapping
  net: mvpp2: replace TX coalescing interrupts with hrtimer

 drivers/net/ethernet/marvell/mvpp2.c | 244 ++++++++++++++++++++++++-----------
 1 file changed, 167 insertions(+), 77 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2015-08-06 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 17:00 Marcin Wojtas [this message]
2015-08-06 17:00 ` [PATCH 1/3] net: mvpp2: remove excessive spinlocks from driver initialization Marcin Wojtas
2015-08-06 17:00 ` [PATCH 2/3] net: mvpp2: enable proper per-CPU TX buffers unmapping Marcin Wojtas
2015-08-06 17:00 ` [PATCH 3/3] net: mvpp2: replace TX coalescing interrupts with hrtimer Marcin Wojtas
2015-08-10 17:57 ` [PATCH 0/3] Fixes for the network driver of Marvell Armada 375 SoC David Miller

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=1438880430-5480-1-git-send-email-mw@semihalf.com \
    --to=mw@semihalf.com \
    --cc=alior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=jaz@semihalf.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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).