From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Jaeden Amero <jaeden.amero@ni.com>
Cc: David Miller <davem@davemloft.net>,
nicolas.ferre@atmel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jeff.westfahl@ni.com,
mihai.neagu@ni.com
Subject: Re: [PATCH RFC] net/macb: Fix UDPv4 checksum offload
Date: Wed, 29 Apr 2015 11:15:21 +0100 [thread overview]
Message-ID: <20150429111521.288902f6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <553FEF66.7010503@ni.com>
> Unfortunately, the Cadence MACB doesn't support the enabling or
> disabling of checksum generation per descriptor.
So how does packet forwarding work ? If that means the device is
re-checksumming packets it is forwarding then that's really not very good
at all, especially if it takes frames that are unchecksummed and corrupts
them with a checksum midflight which is based upon unknown validity.
Other question: you seem to be assuming that the headers in part are
valid. That's not necessarily the case (even for local traffic you can
get UDP frames sent via RAW sockets that are invalid - eg with the ihl
pointing beyond the end of the packet). Given you then write into that
offset isn't a length check needed.
That might also be a useful fast path for longer frames, as you know the
worst case length for a 2 byte UDP frame.
Alan
next prev parent reply other threads:[~2015-04-29 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 22:43 Jaeden Amero
2015-04-28 2:47 ` David Miller
2015-04-28 20:36 ` Jaeden Amero
2015-04-28 20:47 ` David Miller
2015-04-29 10:15 ` One Thousand Gnomes [this message]
2015-04-29 16:03 ` 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=20150429111521.288902f6@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=jaeden.amero@ni.com \
--cc=jeff.westfahl@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.neagu@ni.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.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
all inboxes | Powered by JetHome®