From: David Woodhouse <dwmw2@infradead.org>
To: Tom Herbert <tom@herbertland.com>,
davem@davemloft.net, netdev@vger.kernel.org
Cc: kernel-team@fb.com, ogerlitz@mellanox.com
Subject: Re: [PATCH RFC 0/3] net: Add driver helper function to determine if checksum is offloadable
Date: Thu, 08 Oct 2015 16:09:42 +0100 [thread overview]
Message-ID: <1444316982.92154.2.camel@infradead.org> (raw)
In-Reply-To: <1444088364-2839440-1-git-send-email-tom@herbertland.com>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Mon, 2015-10-05 at 16:39 -0700, Tom Herbert wrote:
> This patch defines a helper function that drivers can call to check
> if it is able to offload the checksum for a particular packet.
It occurs to me that by itself, this doesn't actually fix the problem.
We'd then need to go over all drivers which currently use
NETIF_F_IP_CSUM or NETIF_F_IPV6_CSUM, and convert them. Would that be
the intention?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-10-08 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 23:39 [PATCH RFC 0/3] net: Add driver helper function to determine if checksum is offloadable Tom Herbert
2015-10-05 23:39 ` [PATCH RFC 1/3] net: Add skb_inner_transport_offset function Tom Herbert
2015-10-05 23:39 ` [PATCH RFC 2/3] net: Add driver helper function to determine checksum offloadability Tom Herbert
2015-10-06 3:52 ` Alexander Duyck
2015-10-06 16:31 ` Tom Herbert
2015-10-05 23:39 ` [PATCH RFC 3/3] mlx4: Call skb_csum_offload_check to check offloadability Tom Herbert
2015-10-06 4:03 ` Alexander Duyck
2015-10-06 16:22 ` Tom Herbert
2015-10-06 16:54 ` Alexander Duyck
2015-10-07 15:41 ` Or Gerlitz
2015-10-07 18:07 ` Tom Herbert
2015-10-08 21:39 ` Or Gerlitz
2015-10-06 10:51 ` [PATCH RFC 0/3] net: Add driver helper function to determine if checksum is offloadable David Woodhouse
2015-10-08 15:09 ` David Woodhouse [this message]
2015-10-08 15:48 ` Tom Herbert
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=1444316982.92154.2.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=tom@herbertland.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).