From: Jiri Benc <jbenc@redhat.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Govindarajulu Varadarajan <_govind@gmx.com>,
davem@davemloft.net, netdev@vger.kernel.org, ssujith@cisco.com,
benve@cisco.com, Stefan Assmann <sassmann@redhat.com>
Subject: Re: [PATCH net] enic: fix rx skb checksum
Date: Fri, 19 Dec 2014 11:07:32 +0100 [thread overview]
Message-ID: <20141219110732.53264ef8@griffin> (raw)
In-Reply-To: <17951.1418924367@famine>
On Thu, 18 Dec 2014 09:39:27 -0800, Jay Vosburgh wrote:
> I've actually been looking into this "hw csum failure" (as it
> appears with OVS and VXLAN) the last couple of days, and, at least on
> the sky2 hardware I have, the problem doesn't appear to be the
> hardware's CHECKSUM_COMPLETE checksumming.
With the enic driver, the problem _is_ the hardware checksumming.
While debugging the "hw csum failure" messages, I verified the checksum
returned by the hardware directly in the driver (in
enic_rq_indicate_buf). It appears that for some packets (most notably
ICMP ones), the hardware returns 0xffff. I did not see any other wrong
value, in other words, the returned checksum was either correct, or
0xffff.
I have no idea whether the hardware verified the checksum for the
0xffff case and is just not returning the checksum or whether such
packets come completely unverified.
As for Govindarajulu's patch, I believe we can do better. First, its
description does not match what I'm seeing (I see correct checksum
provided in most cases) and second, the driver should provide
CHECKSUM_COMPLETE whenever possible; and it seems to be possible.
> I've also not tested it on enic hardware. Govindarajulu, would
> you be able to test this against the unmodified enic driver and see if
> it resolves the problem for you?
I'm quite sure it does not, the skb->csum field is incorrect even
before the skb enters the stack.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2014-12-19 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 10:28 [PATCH net] enic: fix rx skb checksum Govindarajulu Varadarajan
2014-12-18 13:58 ` Sergei Shtylyov
2014-12-18 16:26 ` Eric Dumazet
2014-12-18 17:39 ` Jay Vosburgh
2014-12-18 17:49 ` David Miller
2014-12-19 10:07 ` Jiri Benc [this message]
2014-12-19 10:52 ` Govindarajulu Varadarajan
2014-12-19 11:07 ` Jiri Benc
2014-12-19 11:11 ` Jiri Benc
2014-12-19 20:45 ` 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=20141219110732.53264ef8@griffin \
--to=jbenc@redhat.com \
--cc=_govind@gmx.com \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=ssujith@cisco.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).