All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: f.fainelli@gmail.com, vivien.didelot@gmail.com, andrew@lunn.ch,
	davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vladimir Oltean <olteanv@gmail.com>
Subject: [PATCH net-next 0/2] Improvements to the DSA deferred xmit
Date: Fri, 27 Dec 2019 03:42:06 +0200	[thread overview]
Message-ID: <20191227014208.7189-1-olteanv@gmail.com> (raw)

The DSA deferred xmit mechanism is currently used by a single driver
(sja1105) because the transmission of some operations requires SPI
access in the fastpath.

This 2-patch series makes this mechanism better for everybody:

- For those who don't use it, thanks to one less assignment in the
  hotpath
- For those who do, by making its scheduling more amenable and moving it
  outside the generic workqueue (since it still deals with packet
  hotpath, after all)

Vladimir Oltean (2):
  net: dsa: Remove deferred_xmit from dsa_skb_cb
  net: dsa: Create a kernel thread for each port's deferred xmit work

 include/net/dsa.h |  4 ++--
 net/dsa/slave.c   | 53 ++++++++++++++++++++++++++++++++++-------------
 2 files changed, 41 insertions(+), 16 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-12-27  1:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27  1:42 Vladimir Oltean [this message]
2019-12-27  1:42 ` [PATCH net-next 1/2] net: dsa: Remove deferred_xmit from dsa_skb_cb Vladimir Oltean
2019-12-27  1:42 ` [PATCH net-next 2/2] net: dsa: Create a kernel thread for each port's deferred xmit work Vladimir Oltean
2020-01-02 21:49 ` [PATCH net-next 0/2] Improvements to the DSA deferred xmit David Miller
2020-01-02 22:47   ` Vladimir Oltean
2020-01-03 20:10     ` Florian Fainelli
2020-01-04  2:44       ` Richard Cochran

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=20191227014208.7189-1-olteanv@gmail.com \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.