From: Ben Hutchings <bhutchings@solarflare.com>
To: MichałMirosław <mirq-linux@rere.qmqm.pl>
Cc: netdev@vger.kernel.org, Jesse Gross <jesse@nicira.com>
Subject: Re: [PATCH] net: Fix too optimistic NETIF_F_HW_CSUM features
Date: Tue, 30 Nov 2010 15:51:58 +0000 [thread overview]
Message-ID: <1291132318.21077.30.camel@bwh-desktop> (raw)
In-Reply-To: <20101130152838.GA26281@rere.qmqm.pl>
On Tue, 2010-11-30 at 16:28 +0100, MichałMirosław wrote:
[...]
> > > -/**
> > > * pch_gbe_set_tx_csum - Turn transmit checksums on or off
> > > * @netdev: Network interface device structure
> > > * @data: Checksum on[true] or off[false]
> > > @@ -493,11 +481,7 @@ static int pch_gbe_set_tx_csum(struct net_device *netdev, u32 data)
> > > struct pch_gbe_adapter *adapter = netdev_priv(netdev);
> > >
> > > adapter->tx_csum = data;
> > > - if (data)
> > > - netdev->features |= NETIF_F_HW_CSUM;
> > > - else
> > > - netdev->features &= ~NETIF_F_HW_CSUM;
> > > - return 0;
> > > + return ethtool_op_set_tx_ipv6_csum(netdev, data);
> > > }
> > >
> > > /**
> > > @@ -572,7 +556,6 @@ static const struct ethtool_ops pch_gbe_ethtool_ops = {
> > > .set_pauseparam = pch_gbe_set_pauseparam,
> > > .get_rx_csum = pch_gbe_get_rx_csum,
> > > .set_rx_csum = pch_gbe_set_rx_csum,
> > > - .get_tx_csum = pch_gbe_get_tx_csum,
> > > .set_tx_csum = pch_gbe_set_tx_csum,
> > > .get_strings = pch_gbe_get_strings,
> > > .get_ethtool_stats = pch_gbe_get_ethtool_stats,
> >
> > pch_gbe_get_tx_csum can simply be replaced with
> > ethtool_op_set_tx_ipv6_csum.
>
> pch_gbe_set_tx_csum() also changes adapter->tx_csum, which I didn't want
> to touch in this patch. (I'm assuming you mean ...set_tx_csum not ...get_tx_csum).
Sorry, I missed that.
[...]
> > Why are you disabling IPv6 checksum offload? From a quick look at the
> > driver, I think the hardware does support it.
>
> In vxge_xmit() (at drivers/net/vxge/vxge-main.c:922 in net-next) there
> is the following code, that suggested otherwise:
>
> if (skb->ip_summed == CHECKSUM_PARTIAL)
> vxge_hw_fifo_txdl_cksum_set_bits(dtr,
> VXGE_HW_FIFO_TXD_TX_CKO_IPV4_EN |
> VXGE_HW_FIFO_TXD_TX_CKO_TCP_EN |
> VXGE_HW_FIFO_TXD_TX_CKO_UDP_EN);
I bet IPV4_EN refers to the IPv4 header checksum. Since IPv6 doesn't
have a header checksum, there won't be a flag for it here.
> > > diff --git a/net/core/dev.c b/net/core/dev.c
> > > index 3259d2c..622f85a 100644
> > > --- a/net/core/dev.c
> > > +++ b/net/core/dev.c
> > > @@ -5041,10 +5041,13 @@ unsigned long netdev_fix_features(unsigned long features, const char *name)
> > > }
> > >
> > > if (features & NETIF_F_UFO) {
> > > - if (!(features & NETIF_F_GEN_CSUM)) {
> > > + /* maybe split UFO into V4 and V6? */
> > > + if (!((features & NETIF_F_GEN_CSUM) ||
> > > + (features & (NETIF_F_IP_CSUM|NETIF_F_IPV6_CSUM))
> > > + == (NETIF_F_IP_CSUM|NETIF_F_IPV6_CSUM))) {
> > > if (name)
> > > printk(KERN_ERR "%s: Dropping NETIF_F_UFO "
> > > - "since no NETIF_F_HW_CSUM feature.\n",
> > > + "since no checksum offload features.\n",
> > > name);
> > > features &= ~NETIF_F_UFO;
> > > }
> > > diff --git a/net/core/ethtool.c b/net/core/ethtool.c
> > > index 956a9f4..d5bc2881 100644
> > > --- a/net/core/ethtool.c
> > > +++ b/net/core/ethtool.c
> > > @@ -1171,7 +1171,9 @@ static int ethtool_set_ufo(struct net_device *dev, char __user *useraddr)
> > > return -EFAULT;
> > > if (edata.data && !(dev->features & NETIF_F_SG))
> > > return -EINVAL;
> > > - if (edata.data && !(dev->features & NETIF_F_HW_CSUM))
> > > + if (edata.data && !((dev->features & NETIF_F_GEN_CSUM) ||
> > > + (dev->features & (NETIF_F_IP_CSUM|NETIF_F_IPV6_CSUM))
> > > + == (NETIF_F_IP_CSUM|NETIF_F_IPV6_CSUM)))
> > > return -EINVAL;
> > > return dev->ethtool_ops->set_ufo(dev, edata.data);
> > > }
> > I believe UFO is for IPv4 only; IPv6 has an entirely different kind of
> > fragmentation. So I think the check should be dev->features &
> > NETIF_F_V4_CSUM.
>
> net/ipv6/ip6_output.c references NETIF_F_UFO without checking
> IPv6 checksumming features.
Got it.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-30 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 18:17 Broken TX checksumming offloads Michał Mirosław
2010-11-29 19:13 ` Ben Hutchings
2010-11-30 2:35 ` Jesse Gross
2010-11-30 14:23 ` MichałMirosław
2010-11-30 14:23 ` [PATCH] net: Fix drivers advertising HW_CSUM feature to use csum_start MichałMirosław
2010-11-30 14:23 ` [PATCH] net: Fix too optimistic NETIF_F_HW_CSUM features MichałMirosław
[not found] ` <1291130005.21077.18.camel@bwh-desktop>
2010-11-30 15:28 ` MichałMirosław
2010-11-30 15:41 ` Michał Mirosław
2010-11-30 16:12 ` Jon Mason
2010-11-30 15:51 ` Ben Hutchings [this message]
2010-11-30 16:18 ` MichałMirosław
2010-11-30 16:38 ` [PATCH v2] " MichałMirosław
2010-11-30 16:53 ` Eric Dumazet
2010-11-30 17:07 ` MichałMirosław
2010-11-30 17:15 ` MichałMirosław
2010-11-30 17:17 ` Eric Dumazet
2010-12-02 0:44 ` Jon Mason
2010-12-06 21:01 ` David Miller
2010-11-30 14:23 ` [PATCH] net: Move check of checksum features to netdev_fix_features() MichałMirosław
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=1291132318.21077.30.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=jesse@nicira.com \
--cc=mirq-linux@rere.qmqm.pl \
--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