From: Joe Stringer <joestringer@nicira.com>
To: "Vick, Matthew" <matthew.vick@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
Linux NICS <Linux-nics@isotope.jf.intel.com>,
"shahed.shaikh" <shahed.shaikh@qlogic.com>,
"sathya.perla" <sathya.perla@emulex.com>,
Linux Netdev List <netdev@vger.kernel.org>,
Vadai <amirv@mellanox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Tom Herbert <therbert@google.com>,
"dept-gelinuxnicdev" <Dept-GELinuxNICDev@qlogic.com>,
Or Gerlitz <gerlitz.or@gmail.com>,
"Amir@isotope.jf.intel.com" <Amir@isotope.jf.intel.com>
Subject: Re: [linux-nics] [PATCH net 3/5] fm10k: Implement ndo_gso_check()
Date: Fri, 7 Nov 2014 17:51:32 +1300 [thread overview]
Message-ID: <201411071751.33390.joestringer@nicira.com> (raw)
In-Reply-To: <D0815B72.5EAF9%matthew.vick@intel.com>
On Fri, 07 Nov 2014 14:20:08 Vick, Matthew wrote:
> On 11/6/14, 4:55 PM, "Joe Stringer" <joestringer@nicira.com> wrote:
> >On Thu, Nov 06, 2014 at 11:58:32PM +0000, Vick, Matthew wrote:
> >> On 11/5/14, 11:36 AM, "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
> >>
> >>wrote:
> >> Hi Joe, fm10k's hardware is pretty lax about the header size. As long as
> >> the total header length (outer+inner) is 184 bytes or less we're golden,
> >> so if I'm not mistaken that leaves us with a max of 130 bytes beyond the
> >> tunnel header.
> >
> >Oh, okay. To be more explicit, in the case of UDP tunnels I take it that
> >you're talking about L2+L3+(L4+)tunnel+L2+L3+L4 <= 184? (L4 perhaps
> >optional depending on the tunnel protocol used)
> >
> >In that case, the fm10k_gso_check would use something closer to
> >"skb_inner_transport_header(skb) - skb_mac_header(skb) > 184", or
> >perhaps 164 to allow for inner L4 header (?).
> >
> >Joe
>
> Yes, I'm talking about the full shebang.
>
> I like the 164 check, personally (with appropriate #define for
> readability).
Thanks for the feedback, I take it that this approach is preferable over the
other one involving an skb_gso_check() + fm10k_tx_encap_offload() call?
next prev parent reply other threads:[~2014-11-07 4:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 21:56 [PATCH net 0/5] Implement ndo_gso_check() for vxlan nics Joe Stringer
2014-11-04 21:56 ` [PATCH net 1/5] be2net: Implement ndo_gso_check() Joe Stringer
2014-11-04 21:56 ` [PATCH net 2/5] i40e: " Joe Stringer
2014-11-04 23:45 ` Jesse Gross
2014-11-05 12:37 ` Jeff Kirsher
2014-11-20 19:16 ` Joe Stringer
2014-11-20 20:14 ` Jesse Gross
2014-11-05 12:35 ` Jeff Kirsher
2014-11-04 21:56 ` [PATCH net 3/5] fm10k: " Joe Stringer
2014-11-05 12:34 ` [linux-nics] " Jeff Kirsher
2014-11-05 12:44 ` Or Gerlitz
2014-11-05 12:47 ` Jeff Kirsher
[not found] ` <CANr6G5xBehKGVozOAM=m8CXY7Q8_kPu-s5zgwho4=npv=bQsrg@mail.gmail.com>
2014-11-05 19:36 ` Jeff Kirsher
[not found] ` <D0814A3F.5EA53%matthew.vick@intel.com>
2014-11-07 0:55 ` Joe Stringer
[not found] ` <D0815B72.5EAF9%matthew.vick@intel.com>
2014-11-07 4:51 ` Joe Stringer [this message]
2014-11-06 2:54 ` Alexander Duyck
2014-11-06 18:41 ` Joe Stringer
2014-11-06 21:15 ` Joe Stringer
2014-11-07 1:07 ` Vick, Matthew
2014-11-07 5:05 ` Joe Stringer
2014-11-07 19:49 ` Vick, Matthew
2014-11-07 22:35 ` Joe Stringer
2014-11-08 0:51 ` Vick, Matthew
2014-11-04 21:56 ` [PATCH net 4/5] net/mlx4_en: " Joe Stringer
2014-11-05 12:41 ` Or Gerlitz
2014-11-04 21:56 ` [PATCH net 5/5] qlcnic: " Joe Stringer
2014-11-05 9:17 ` Shahed Shaikh
2014-11-05 12:38 ` [PATCH net 0/5] Implement ndo_gso_check() for vxlan nics Or Gerlitz
[not found] ` <CANr6G5xtNYenhd8KDWx+kRcnSZ0fahUdAL+6Wcz=5_dNvrQR6Q@mail.gmail.com>
2014-11-05 18:00 ` Tom Herbert
2014-11-05 21:32 ` Or Gerlitz
2014-11-05 21:38 ` David Miller
2014-11-06 1:06 ` Joe Stringer
2014-11-06 2:15 ` David Miller
2014-11-06 2:44 ` Tom Herbert
2014-11-06 8:23 ` Or Gerlitz
[not found] ` <CF9D1877D81D214CB0CA0669EFAE020C68CC79EF@CMEXMB1.ad.emulex.com>
2014-11-06 16:06 ` Tom Herbert
2014-11-06 16:15 ` Jesse Gross
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=201411071751.33390.joestringer@nicira.com \
--to=joestringer@nicira.com \
--cc=Amir@isotope.jf.intel.com \
--cc=Dept-GELinuxNICDev@qlogic.com \
--cc=Linux-nics@isotope.jf.intel.com \
--cc=amirv@mellanox.com \
--cc=gerlitz.or@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.vick@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@emulex.com \
--cc=shahed.shaikh@qlogic.com \
--cc=therbert@google.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
all inboxes | Powered by JetHome®