netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: netdev@vger.kernel.org, dcaratti@redhat.com,
	lucien.xin@gmail.com, linux-sctp@vger.kernel.org
Subject: Re: SCTP over GRE (w csum)
Date: Mon, 23 Dec 2019 14:49:04 -0300	[thread overview]
Message-ID: <20191223174904.GL4444@localhost.localdomain> (raw)
In-Reply-To: <20191223174535.GF6274@localhost.localdomain>

[ Just Cc-ing linux-sctp@ ]

On Mon, Dec 23, 2019 at 06:45:35PM +0100, Lorenzo Bianconi wrote:
> Hi all,
> 
> I am currently working on the following scenario:
> 
> sctp --> ipv4 --> gretap --> ipv6 --> eth
> 
> If NETIF_F_SCTP_CRC is not supported by the network device (it is the
> case for gre), sctp will fallback computing the crc32 in sw with
> sctp_gso_make_checksum(), where SKB_GSO_CB(skb)->csum is set to ~0 by
> gso_reset_checksum(). After the gso segmentation, gre_gso_segment()
> will try to compute gre csum with gso_make_checksum() even if skb->ip_summed
> is set to CHECKSUM_NONE (and so using ~0 as partial).
> One possible (trivial and not tested) solution would be to recompute the
> gre checksum, doing in gre_gso_segment() something like:
> 
> 	if (skb->ip_summed == CHECKSUM_NONE) {
> 		...
> 		err = skb_checksum_help(skb);
> 		if (err < 0)
> 			return return ERR_PTR(err);
> 	} else {
> 		*pcsum = gso_make_checksum(skb, 0);
> 	}
> 
> One possible improvement would be offload the GRE checksum computation if the
> hw exports this capability in netdev_features and fall back to the sw
> implementation if not.
> Am I missing something? Is there a better approach?
> 
> Regards,
> Lorenzo



      reply	other threads:[~2019-12-23 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 17:45 SCTP over GRE (w csum) Lorenzo Bianconi
2019-12-23 17:49 ` Marcelo Ricardo Leitner [this message]

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=20191223174904.GL4444@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=dcaratti@redhat.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lucien.xin@gmail.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).