netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>, Nix <nix@esperi.org.uk>,
	Roger.Luethi.rl@hellgate.ch,
	Bjarke Istrup Pedersen <gurligebis@gentoo.org>
Subject: [PATCH net-next #3 0/8] via-rhine rework
Date: Fri,  1 May 2015 22:14:37 +0200	[thread overview]
Message-ID: <cover.1430509434.git.romieu@fr.zoreil.com> (raw)

The series applies against davem-next as of
9dd3c797496affd699805c8a9d8429ad318c892f ("drivers: net: xgene: fix kbuild
warnings").

Patches #1..#4 avoid holes in the receive ring.

Patch #5 is a small leftover cleanup for #1..#4.

Patches #6 and #7 are fairly simple barrier stuff.

Patch #8 closes some SMP transmit races - not that anyone really
complained about these but it's a bit hard to handwave that they
can be safely ignored. Some testing, especially SMP testing of
course, would be welcome.

. Changes since #2:
  - added dma_rmb barrier in vlan related patch 6.
  - s/wmb/dma_wmb/ in (*new*) patch 7 of 8.
  - added explicit SMP barriers in (*new*) patch 8 of 8.

. Changes since #1:
  - turned wmb() into dma_wmb() as suggested by davem and Alexander Duyck
    in patch 1 of 6.
  - forgot to reset rx_head_desc in rhine_reset_rbufs in patch 4 of 6.
  - removed rx_head_desc altogether in (*new*) patch 5 of 6
  - remoed some vlan receive uglyness in (*new*) patch 6 of 6.


Francois Romieu (8):
  via-rhine: commit receive buffer address before descriptor status update.
  via-rhine: allocate and map receive buffer in a single transaction
  via-rhine: gotoize rhine_open error path.
  via-rhine: forbid holes in the receive descriptor ring.
  via-rhine: kiss rx_head_desc goodbye.
  via-rhine: add consistent memory barrier in vlan receive code.
  via-rhine: dma_wmb transmit barrier.
  via-rhine: close SMP transmit races.

 drivers/net/ethernet/via/via-rhine.c | 249 +++++++++++++++++++++++------------
 1 file changed, 162 insertions(+), 87 deletions(-)

-- 
Ueimor

             reply	other threads:[~2015-05-01 20:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 20:14 Francois Romieu [this message]
2015-05-01 20:14 ` [PATCH net-next #3 1/8] via-rhine: commit receive buffer address before descriptor status update Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 2/8] via-rhine: allocate and map receive buffer in a single transaction Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 3/8] via-rhine: gotoize rhine_open error path Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 4/8] via-rhine: forbid holes in the receive descriptor ring Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 5/8] via-rhine: kiss rx_head_desc goodbye Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 6/8] via-rhine: add consistent memory barrier in vlan receive code Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 7/8] via-rhine: dma_wmb transmit barrier Francois Romieu
2015-05-01 20:14 ` [PATCH net-next #3 8/8] via-rhine: close SMP transmit races Francois Romieu
2015-05-04  4:18 ` [PATCH net-next #3 0/8] via-rhine rework 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=cover.1430509434.git.romieu@fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=Roger.Luethi.rl@hellgate.ch \
    --cc=davem@davemloft.net \
    --cc=gurligebis@gentoo.org \
    --cc=netdev@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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).