diff options
author | Jesse Gross <jesse@nicira.com> | 2014-12-24 07:37:26 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-12-26 23:20:56 +0100 |
commit | 5f35227ea34bb616c436d9da47fc325866c428f3 (patch) | |
tree | e6f997cb2f1f1bce1d2b5be613e1be667b9f927f /drivers/dma-buf | |
parent | net: incorrect use of init_completion fixup (diff) | |
download | linux-5f35227ea34bb616c436d9da47fc325866c428f3.tar.xz linux-5f35227ea34bb616c436d9da47fc325866c428f3.zip |
net: Generalize ndo_gso_check to ndo_features_check
GSO isn't the only offload feature with restrictions that
potentially can't be expressed with the current features mechanism.
Checksum is another although it's a general issue that could in
theory apply to anything. Even if it may be possible to
implement these restrictions in other ways, it can result in
duplicate code or inefficient per-packet behavior.
This generalizes ndo_gso_check so that drivers can remove any
features that don't make sense for a given packet, similar to
netif_skb_features(). It also converts existing driver
restrictions to the new format, completing the work that was
done to support tunnel protocols since the issues apply to
checksums as well.
By actually removing features from the set that are used to do
offloading, it solves another problem with the existing
interface. In these cases, GSO would run with the original set
of features and not do anything because it appears that
segmentation is not required.
CC: Tom Herbert <therbert@google.com>
CC: Joe Stringer <joestringer@nicira.com>
CC: Eric Dumazet <edumazet@google.com>
CC: Hayes Wang <hayeswang@realtek.com>
Signed-off-by: Jesse Gross <jesse@nicira.com>
Acked-by: Tom Herbert <therbert@google.com>
Fixes: 04ffcb255f22 ("net: Add ndo_gso_check")
Tested-by: Hayes Wang <hayeswang@realtek.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/dma-buf')
0 files changed, 0 insertions, 0 deletions