From: Joe Stringer <joestringer@nicira•com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel•com>,
Shannon Nelson <shannon.nelson@intel•com>,
Jesse Brandeburg <jesse.brandeburg@intel•com>
Cc: netdev@vger•kernel.org, matthew.vick@intel•com,
linux.nics@intel•com, therbert@google•com, gerlitz.or@gmail•com,
alexander.duyck@gmail•com, linux-kernel@vger•kernel.org
Subject: Re: [PATCHv2 net 2/2] fm10k: Implement ndo_gso_check()
Date: Thu, 13 Nov 2014 15:52:19 -0800 [thread overview]
Message-ID: <20141113235219.GA35957@gmail.com> (raw)
In-Reply-To: <1415922116.2454.34.camel@jtkirshe-mobl>
On Thu, Nov 13, 2014 at 03:41:56PM -0800, Jeff Kirsher wrote:
> On Thu, 2014-11-13 at 15:36 -0800, Joe Stringer wrote:
> > ndo_gso_check() was recently introduced to allow NICs to report the
> > offloading support that they have on a per-skb basis. Add an
> > implementation for this driver which checks for something that looks
> > like VXLAN.
> >
> > Signed-off-by: Joe Stringer <joestringer@nicira•com>
> > ---
> > v2: Reuse fm10k_tx_encap_offload().
> > ---
> > drivers/net/ethernet/intel/fm10k/fm10k.h | 1 +
> > drivers/net/ethernet/intel/fm10k/fm10k_main.c | 2 +-
> > drivers/net/ethernet/intel/fm10k/fm10k_netdev.c | 8 ++++++++
> > 3 files changed, 10 insertions(+), 1 deletion(-)
>
> Same with this one as well, thanks Joe.
Thanks Jeff.
Could you remind me, is the equivalent i40e patch on your queue or were
we still waiting on further feedback from Shannon/Jesse?
next prev parent reply other threads:[~2014-11-13 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 23:36 [PATCHv2 net 1/2] fm10k: Check tunnel header length in encap offload Joe Stringer
2014-11-13 23:36 ` [PATCHv2 net 2/2] fm10k: Implement ndo_gso_check() Joe Stringer
2014-11-13 23:41 ` Jeff Kirsher
2014-11-13 23:52 ` Joe Stringer [this message]
2014-11-14 0:12 ` Jeff Kirsher
2014-11-14 0:29 ` Joe Stringer
2014-11-13 23:41 ` [PATCHv2 net 1/2] fm10k: Check tunnel header length in encap offload Jeff Kirsher
2014-11-14 0:41 ` Vick, Matthew
2014-11-14 0:54 ` Joe Stringer
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=20141113235219.GA35957@gmail.com \
--to=joestringer@nicira$(echo .)com \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=gerlitz.or@gmail$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux.nics@intel$(echo .)com \
--cc=matthew.vick@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shannon.nelson@intel$(echo .)com \
--cc=therbert@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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