mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/9] Reduce usage of NetRxPackets[]
Date: Mon, 19 Sep 2022 10:01:24 +0200	[thread overview]
Message-ID: <20220919080133.877651-1-s.hauer@pengutronix.de> (raw)

Usage of the globally allocted network receive buffers NetRxPackets[] is
inherently broken. Some drivers queue these buffers in the hardware.
When multiple of these drivers are active at the same time then they
stamp over each others packets and bad things happen.

The goal is to remove NetRxPackets[] entirely in favor of per device
packet buffers. This series is a first step into that direction. It
removes the simple cases where only NetRxPackets[0] is used to store the
single packet that is pulled out of the hardware before net_receive() is
called.

Sascha

Sascha Hauer (9):
  net: tap: Allocate own receive buffer
  net: macb: Allocate own receive buffer
  net: cs8900: Allocate own receive buffer
  net: liteeth: Do not use NetRxPackets
  net: efi-snp: Allocate own receive buffer
  net: smc91111: Allocate own receive buffer
  net: smc911x: Allocate own receive buffer
  net: ks8851_mll: Allocate own receive buffer
  net: remove altera_tse driver

 drivers/net/Kconfig      |  16 --
 drivers/net/Makefile     |   1 -
 drivers/net/altera_tse.c | 563 ---------------------------------------
 drivers/net/altera_tse.h | 296 --------------------
 drivers/net/cs8900.c     |   7 +-
 drivers/net/efi-snp.c    |   6 +-
 drivers/net/ks8851_mll.c |   9 +-
 drivers/net/liteeth.c    |   8 +-
 drivers/net/macb.c       |  12 +-
 drivers/net/smc91111.c   |  10 +-
 drivers/net/smc911x.c    |   8 +-
 drivers/net/tap.c        |   7 +-
 12 files changed, 45 insertions(+), 898 deletions(-)
 delete mode 100644 drivers/net/altera_tse.c
 delete mode 100644 drivers/net/altera_tse.h

-- 
2.30.2




             reply	other threads:[~2022-09-19  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  8:01 Sascha Hauer [this message]
2022-09-19  8:01 ` [PATCH 1/9] net: tap: Allocate own receive buffer Sascha Hauer
2022-09-19  8:01 ` [PATCH 2/9] net: macb: " Sascha Hauer
2022-09-19  8:01 ` [PATCH 3/9] net: cs8900: " Sascha Hauer
2022-09-19  8:01 ` [PATCH 4/9] net: liteeth: Do not use NetRxPackets Sascha Hauer
2022-09-19  8:01 ` [PATCH 5/9] net: efi-snp: Allocate own receive buffer Sascha Hauer
2022-09-19  8:01 ` [PATCH 6/9] net: smc91111: " Sascha Hauer
2022-09-19  8:01 ` [PATCH 7/9] net: smc911x: " Sascha Hauer
2022-09-19  8:01 ` [PATCH 8/9] net: ks8851_mll: " Sascha Hauer
2022-09-19  8:01 ` [PATCH 9/9] net: remove altera_tse driver Sascha Hauer

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=20220919080133.877651-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox