From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: mst@redhat.com, Vlad Yasevich <vyasevic@redhat.com>
Subject: [PATCH v4 0/3] Correctly perform offloads when VNET_HDR is disabled
Date: Fri, 16 Aug 2013 15:24:59 -0400 [thread overview]
Message-ID: <1376681102-19753-1-git-send-email-vyasevic@redhat.com> (raw)
Changes since v3:
- The main change here is that instead of mucking around with checksum bits,
we instead treat macvtap as macvlan+tap each with separate feature sets.
tap_features identify the features of only the 'tap' part and we only use
them when forwarding, essentially making the 'tap' part a pseudo-device.
To properly handle GSO, we always set NETIF_F_SG | NETIF_F_GSO on the
'tap' part.
- The rest of the set is mostly the same in that we allow user to change
tap offload features whether VNET_HDR is set or cleared.
- When VNET_HDR is disabled, we ignore user specified tap offloads. This
is now a separate patch so that if there are disagreements, it can
be easily dropped.
Vlad Yasevich (3):
macvtap: simplify usage of tap_features
macvtap: Correctly set tap features when IFF_VNET_HDR is disabled.
macvtap: Ignore tap features when VNET_HDR is off
drivers/net/macvtap.c | 33 ++++++++++++++++++++++++---------
1 file changed, 24 insertions(+), 9 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-08-16 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 19:24 Vlad Yasevich [this message]
2013-08-16 19:25 ` [PATCH v4 1/3] macvtap: simplify usage of tap_features Vlad Yasevich
2013-08-20 20:09 ` David Miller
2013-08-16 19:25 ` [PATCH v4 2/3] macvtap: Correctly set tap features when IFF_VNET_HDR is disabled Vlad Yasevich
2013-08-20 20:09 ` David Miller
2013-08-16 19:25 ` [PATCH v4 3/3] macvtap: Ignore tap features when VNET_HDR is off Vlad Yasevich
2013-08-20 20:09 ` David Miller
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=1376681102-19753-1-git-send-email-vyasevic@redhat.com \
--to=vyasevic@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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).