From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] net: core: remove TX_LOCKED support
Date: Tue, 26 Apr 2016 15:53:29 -0400 (EDT) [thread overview]
Message-ID: <20160426.155329.174600162183067810.davem@davemloft.net> (raw)
In-Reply-To: <1461526694-11367-1-git-send-email-fw@strlen.de>
From: Florian Westphal <fw@strlen.de>
Date: Sun, 24 Apr 2016 21:38:08 +0200
> Not that many users left, lets kill it.
>
> TX_LOCKED was meant to be used by LLTX drivers when spin_trylock()
> failed. Stack then re-queued if collisions happened on different
> cpus or free'd the skb to prevent deadlocks.
>
> Most of the driver removal patches fall into one of three categories:
> 1. remove the driver-private tx lock (and LLTX flag), or...
> 2. convert spin_trylock to plain spin_lock, or...
> 3. convert TX_LOCKED to free+TX_OK
>
> Patches are grouped by these categories, last patch is the actual removal.
> All driver changes were compile tested only with exception of atl1e.
This looks good to me, series applied, thanks Florian.
prev parent reply other threads:[~2016-04-26 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 19:38 [PATCH net-next 0/6] net: core: remove TX_LOCKED support Florian Westphal
2016-04-24 19:38 ` [PATCH net-next 1/6] RDMA/nes: remove use of NETDEV_TX_LOCKED Florian Westphal
2016-04-24 19:38 ` [PATCH net-next 2/6] atl1c: remove private tx lock Florian Westphal
2016-04-24 22:03 ` Francois Romieu
2016-04-24 22:05 ` Francois Romieu
2016-04-25 15:43 ` Florian Westphal
2016-04-25 23:16 ` Francois Romieu
2016-04-24 19:38 ` [PATCH net-next 3/6] atle1: remove LLTX support and TX_UNLOCKED Florian Westphal
2016-04-24 19:38 ` [PATCH net-next 4/6] drivers: net: use NETDEV_TX_OK instead of NETDEV_TX_LOCKED Florian Westphal
2016-04-24 19:38 ` [PATCH net-next 5/6] drivers: net: remove NETDEV_TX_LOCKED Florian Westphal
2016-04-24 19:38 ` [PATCH net-next 6/6] net: remove NETDEV_TX_LOCKED support Florian Westphal
2016-04-26 19:53 ` David Miller [this message]
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=20160426.155329.174600162183067810.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).