All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: R W van Schagen <vschagen@cs.com>
Cc: netdev@vger.kernel.org
Subject: Re: DSA slaves not inheriting hw_enc_features and xfrmdev_ops?
Date: Thu, 21 Oct 2021 15:11:32 +0200	[thread overview]
Message-ID: <YXFnBHFlOt8AvcLe@lunn.ch> (raw)
In-Reply-To: <A08F0571-5705-4FD6-9C5D-55B4C0734712@cs.com>

> Thanks for the explanation. For now I will proceed using notifier callbacks.
> 
> One more strange thing I am noticing: Even if I set NETIF_F_GSO_ESP
> I am still not getting any GSO packets (skb_is_gso is always false) so my
> transmit speeds are like 2/3 of the receive speeds. Hardware Decryption vs
> Encryption is not 100% the same, but it is close.
> 
> I am getting the esp_gro_receive callbacks, but not the esp_gso_segment,
> BUT: for some reason my packets still get TCP GSO.

I'm not too familiar with GSO. But my understanding is that you create
a template set of headers which need to be placed onto each frame when
the segmentation actually happens. For DSA, that template would need
to include the DSA header. As far as i understand, there is nothing in
the DSA core that allows for adding the DSA headers into the template.
So you might be able to do GSO at the slave interface, but when the
slave passes frames to the master, you then require segmentation to
happen, so the tag driver can add the DSA header.

	Andrew


      reply	other threads:[~2021-10-21 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CDEC9628-69B6-4A83-81CF-34407070214F.ref@cs.com>
2021-10-20  1:28 ` DSA slaves not inheriting hw_enc_features and xfrmdev_ops? R W van Schagen
2021-10-20 12:06   ` Andrew Lunn
2021-10-21 12:13     ` R W van Schagen
2021-10-21 13:11       ` Andrew Lunn [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=YXFnBHFlOt8AvcLe@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=vschagen@cs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.