From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
jiri@resnulli.us, j.vosburgh@gmail.com, vfalico@gmail.com,
andy@greyhouse.net
Subject: Re: [PATCH net-next 0/8] nfp: offload LAG for tc flower egress
Date: Thu, 24 May 2018 23:11:24 -0400 (EDT) [thread overview]
Message-ID: <20180524.231124.355200569385885289.davem@davemloft.net> (raw)
In-Reply-To: <20180524022255.18548-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Wed, 23 May 2018 19:22:47 -0700
> This series from John adds bond offload to the nfp driver. Patch 5
> exposes the hash type for NETDEV_LAG_TX_TYPE_HASH to make sure nfp
> hashing matches that of the software LAG. This may be unnecessarily
> conservative, let's see what LAG maintainers think :)
Series applied, thanks.
next prev parent reply other threads:[~2018-05-25 3:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 2:22 [PATCH net-next 0/8] nfp: offload LAG for tc flower egress Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 1/8] nfp: add ndo_set_mac_address for representors Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 2/8] nfp: nfpcore: add rtsym writing function Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 3/8] nfp: flower: check for/turn on LAG support in firmware Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 4/8] nfp: flower: add per repr private data for LAG offload Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 5/8] net: include hash policy in LAG changeupper info Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 6/8] nfp: flower: monitor and offload LAG groups Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 7/8] nfp: flower: implement host cmsg handler for LAG Jakub Kicinski
2018-05-24 2:22 ` [PATCH net-next 8/8] nfp: flower: compute link aggregation action Jakub Kicinski
2018-05-24 17:09 ` Or Gerlitz
2018-05-24 17:36 ` John Hurley
2018-05-24 17:04 ` [PATCH net-next 0/8] nfp: offload LAG for tc flower egress Or Gerlitz
2018-05-24 18:23 ` Samudrala, Sridhar
2018-05-24 18:53 ` Jakub Kicinski
2018-05-24 18:49 ` Jakub Kicinski
2018-05-24 19:26 ` Or Gerlitz
2018-05-24 22:01 ` Jakub Kicinski
2018-05-25 3:11 ` David Miller [this message]
2018-05-25 6:48 ` Jiri Pirko
2018-05-26 2:47 ` Jakub Kicinski
2018-05-29 14:08 ` John Hurley
2018-05-29 22:09 ` Jiri Pirko
2018-05-30 9:26 ` John Hurley
2018-05-30 20:29 ` Jiri Pirko
2018-05-31 10:20 ` John Hurley
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=20180524.231124.355200569385885289.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=vfalico@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.