From: Yi Zou <yi.zou@intel.com>
To: netdev@vger.kernel.org
Cc: devel@open-fcoe.org, bhutchings@solarflare.com,
jeffrey.t.kirsher@intel.com
Subject: [PATCH] net: update the usage of CHECKSUM_UNNECESSARY
Date: Mon, 19 Mar 2012 14:12:41 -0700 [thread overview]
Message-ID: <20120319211241.11291.53271.stgit@localhost6.localdomain6> (raw)
As suggested by Ben, this adds the clarification on the usage of
CHECKSUM_UNNECESSARY on the outgoing patch. Also add the usage
description of NETIF_F_FCOE_CRC and CHECKSUM_UNNECESSARY
for the kernel FCoE protocol driver.
This is a follow-up to the following:
http://patchwork.ozlabs.org/patch/147315/
Signed-off-by: Yi Zou <yi.zou@intel.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: www.Open-FCoE.org <devel@open-fcoe.org>
---
include/linux/skbuff.h | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 8dc8257..a2b9953 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -94,6 +94,13 @@
* about CHECKSUM_UNNECESSARY. 8)
* NETIF_F_IPV6_CSUM about as dumb as the last one but does IPv6 instead.
*
+ * UNNECESSARY: device will do per protocol specific csum. Protocol drivers
+ * that do not want net to perform the checksum calculation should use
+ * this flag in their outgoing skbs.
+ * NETIF_F_FCOE_CRC this indicates the device can do FCoE FC CRC
+ * offload. Correspondingly, the FCoE protocol driver
+ * stack should use CHECKSUM_UNNECESSARY.
+ *
* Any questions? No questions, good. --ANK
*/
next reply other threads:[~2012-03-19 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 21:12 Yi Zou [this message]
2012-03-19 21:38 ` [PATCH] net: update the usage of CHECKSUM_UNNECESSARY David Miller
2012-05-08 17:48 ` Michael S. Tsirkin
[not found] ` <20120508174831.GA27406-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-05-08 18:20 ` Ben Hutchings
2012-05-09 6:03 ` Michael S. Tsirkin
2012-05-10 0:05 ` Ben Hutchings
2012-05-10 6:00 ` Michael S. Tsirkin
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=20120319211241.11291.53271.stgit@localhost6.localdomain6 \
--to=yi.zou@intel.com \
--cc=bhutchings@solarflare.com \
--cc=devel@open-fcoe.org \
--cc=jeffrey.t.kirsher@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).