From: Chris Leech <christopher.leech@intel.com>
To: netdev@vger.kernel.org
Subject: Question about supporting non-IP offloads (FCoE)
Date: Wed, 24 Sep 2008 13:55:26 -0700 [thread overview]
Message-ID: <48DAA93E.5010102@intel.com> (raw)
I'm looking at adding support for stateless offloads to the Fibre
Channel over Ethernet stack at open-fcoe.org that roughly match
currently supported TCP offloads: Fibre Channel CRC offload on Tx and
Rx, and sequencing offload (GSO) on Tx.
>From the net_device all I see the need for is two feature flags bits for
the transmit path, one for FC-CRC and one for FCoE GSO.
In the skb, the FCoE needs match up well with the existing CRC and GSO
fields. I would like to reuse the ip_summed bits rather than add to the
skb, but I suspect this will be the most controversial part of the FCoE
offloads.
Are there any objections to the idea of adding checks for FCoE protocol
to the dev_queue_xmit/dev_can_checksum/can_checksum_protocol path?
Obviously skb_checksum_help isn't going to work as a software fallback
and a protocol check would need to be added there as well, or a
per-protocol helper like is done for gso_segment.
- Chris
reply other threads:[~2008-09-24 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48DAA93E.5010102@intel.com \
--to=christopher.leech@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).