From: Saeed Mahameed <saeedm@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Tariq Toukan <tariqt@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>, Roi Dayan <roid@mellanox.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Saeed Mahameed <saeedm@mellanox.com>
Subject: [PATCH net-next 0/7] Mellanox 100G mlx5 updates 2016-11-29
Date: Wed, 30 Nov 2016 00:19:25 +0200 [thread overview]
Message-ID: <1480457972-31286-1-git-send-email-saeedm@mellanox.com> (raw)
Hi Dave,
The following series from Tariq and Roi, provides some critical fixes
and updates for the mlx5e driver.
>From Tariq:
- Fix driver coherent memory huge allocation issues by fragmenting
completion queues, in a way that is transparent to the netdev driver by
providing a new buffer type "mlx5_frag_buf" with the same access API.
- Create UMR MKey per RQ to have better scalability.
>From Roi:
- Some fixes for the encap-decap support and tc flower added lately to the
mlx5e driver.
This series was generated against commit:
31ac1c19455f ("geneve: fix ip_hdr_len reserved for geneve6 tunnel.")
Thanks,
Saeed.
Roi Dayan (4):
net/mlx5e: Remove redundant hashtable lookup in configure flower
net/mlx5e: Correct cleanup order when deleting offloaded TC rules
net/mlx5e: Refactor tc del flow to accept mlx5e_tc_flow instance
net/mlx5e: Remove flow encap entry in the correct place
Tariq Toukan (3):
net/mlx5e: Implement Fragmented Work Queue (WQ)
net/mlx5e: Move function mlx5e_create_umr_mkey
net/mlx5e: Create UMR MKey per RQ
drivers/net/ethernet/mellanox/mlx5/core/alloc.c | 66 +++++++++++
drivers/net/ethernet/mellanox/mlx5/core/en.h | 14 +--
.../net/ethernet/mellanox/mlx5/core/en_ethtool.c | 12 +-
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 121 +++++++++++----------
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 82 ++++++--------
drivers/net/ethernet/mellanox/mlx5/core/wq.c | 26 +++--
drivers/net/ethernet/mellanox/mlx5/core/wq.h | 18 ++-
include/linux/mlx5/driver.h | 11 ++
8 files changed, 215 insertions(+), 135 deletions(-)
--
2.7.4
next reply other threads:[~2016-11-29 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 22:19 Saeed Mahameed [this message]
2016-11-29 22:19 ` [PATCH net-next 1/7] net/mlx5e: Implement Fragmented Work Queue (WQ) Saeed Mahameed
2016-11-29 23:31 ` Eric Dumazet
2016-11-30 10:02 ` Tariq Toukan
2016-11-29 22:19 ` [PATCH net-next 2/7] net/mlx5e: Move function mlx5e_create_umr_mkey Saeed Mahameed
2016-11-29 22:19 ` [PATCH net-next 3/7] net/mlx5e: Create UMR MKey per RQ Saeed Mahameed
2016-11-29 22:19 ` [PATCH net-next 4/7] net/mlx5e: Remove redundant hashtable lookup in configure flower Saeed Mahameed
2016-11-29 22:19 ` [PATCH net-next 5/7] net/mlx5e: Correct cleanup order when deleting offloaded TC rules Saeed Mahameed
2016-11-29 22:19 ` [PATCH net-next 6/7] net/mlx5e: Refactor tc del flow to accept mlx5e_tc_flow instance Saeed Mahameed
2016-11-29 22:19 ` [PATCH net-next 7/7] net/mlx5e: Remove flow encap entry in the correct place Saeed Mahameed
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=1480457972-31286-1-git-send-email-saeedm@mellanox.com \
--to=saeedm@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roid@mellanox.com \
--cc=sebott@linux.vnet.ibm.com \
--cc=tariqt@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).