netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: amirv@mellanox.com
Cc: netdev@vger.kernel.org, achiad@mellanox.com,
	ogerlitz@mellanox.com, talal@mellanox.com
Subject: Re: [PATCH net-next 0/8] net/mlx5e: Driver updates 04-Aug-2015
Date: Thu, 06 Aug 2015 22:01:15 -0700 (PDT)	[thread overview]
Message-ID: <20150806.220115.1419958691029162886.davem@davemloft.net> (raw)
In-Reply-To: <1438686347-17370-1-git-send-email-amirv@mellanox.com>

From: Amir Vadai <amirv@mellanox.com>
Date: Tue,  4 Aug 2015 14:05:39 +0300

> This patchset introduces two features to the ConnectX-4 driver: Patch 8/8
> ("Support physical port counters") exposes some hardware counters through
> ethtool. Rest of the patches are preparation and usage of what we call
> light-weight netdev open/close. Some flows that used to be in the ndo_open/stop
> are moved to the PCI probe/remove flows - i.e. we will make the netdev
> open/close operations more "light-weight".
> 
> The benefits of this change are:
> 1) Reduce the execution time of the stop/open operations.
> 2) Avoid saving SW shadows of resource configurations that must
>    persist through stop/open operations (e.g flow table steering
>    rules), and avoid deleting/applying them from/to the device upon
>    netdev stop/open.
> 3) Avoid synchronizing threads that access those resources with the
>    netdev stop/open threads.
> 
> Instead of create/destroy the resource during netdev open/stop, This patchset
> changes the behavior such that upon netdev stop, traffic is redirected to a
> "Drop RQ" (a RQ that silently drops, at the NIC HW level all incoming traffic).
> After redirecting the traffic, RX/TX software resources could be destroyed.
> During netdev open, the RX/TX rings are created and traffic is redirected to
> the RX rings.
> 
> Patchset was applied and tested over commit ba7591d ("ebpf: add skb->hash to
> offset map for usage in {cls, act}_bpf or filters")

Series applied, thanks.

      parent reply	other threads:[~2015-08-07  5:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 11:05 [PATCH net-next 0/8] net/mlx5e: Driver updates 04-Aug-2015 Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 1/8] net/mlx5e: Unify the RX flow Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 2/8] net/mlx5e: Introduce the "Drop RQ" Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 3/8] net/mlx5_core: Introduce access function to modify RSS/LRO params Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 4/8] net/mlx5e: Light-weight netdev open/stop Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 5/8] net/mlx5e: Rename/move functions following the ndo_stop flow change Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 6/8] net/mlx5e: Disable async events before unregister_netdev() Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 7/8] net/mlx5e: Take advantage of the light-weight netdev open/stop Amir Vadai
2015-08-04 11:05 ` [PATCH net-next 8/8] net/mlx5_core: Support physical port counters Amir Vadai
2015-08-07  5:01 ` 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=20150806.220115.1419958691029162886.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=achiad@mellanox.com \
    --cc=amirv@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=talal@mellanox.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).