From: Joseph Gasparakis <joseph.gasparakis@intel.com>
To: davem@davemloft.net, shemminger@vyatta.com, chrisw@sous-sol.org
Cc: Joseph Gasparakis <joseph.gasparakis@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/3 ] tunneling: Add support for hardware-offloaded encapsulation
Date: Thu, 8 Nov 2012 18:18:00 -0800 [thread overview]
Message-ID: <1352427483-4380-1-git-send-email-joseph.gasparakis@intel.com> (raw)
The series contains updates to add in the NIC Rx and Tx checksumming support
for encapsulated packets.
The sk_buff needs to somehow have information of the inner packet, and adding
three fields for the inner mac, network and transport headers was the prefered
approach.
Not adding these fields would mean that the drivers would need to parse the
sk_buff data in hot-path, having a negative impact in the performance.
Adding in sk_buff a pointer to the skbuff of the inner packet made sense, but
would be a complicated change as assumptions needed to be made with regards to
helper functions such as skb_clone() skb_copy(). Also code for the existing
encapsulation protocols (such as VXLAN and IP GRE) had to be reworked, so the
decision was to have the simple approach of adding these three fields.
next reply other threads:[~2012-11-09 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 2:18 Joseph Gasparakis [this message]
2012-11-09 2:18 ` [PATCH 1/3] net: Add support for hardware-offloaded encapsulation Joseph Gasparakis
2012-11-14 12:23 ` Dmitry Kravkov
2012-11-09 2:18 ` [PATCH 2/3] vxlan: capture inner headers during encapsulation Joseph Gasparakis
2012-11-09 2:18 ` [PATCH 3/3] ipgre: " Joseph Gasparakis
2012-11-11 15:18 ` Dmitry Kravkov
2012-11-12 1:47 ` Joseph Gasparakis
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=1352427483-4380-1-git-send-email-joseph.gasparakis@intel.com \
--to=joseph.gasparakis@intel.com \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).