public inbox for [email protected]
 help / color / mirror / Atom feed
From: Gaurav Jain <[email protected]>
To: Steffen Trumtrar <[email protected]>,
	Jakub Kicinski <[email protected]>
Cc: Marc Kleine-Budde <[email protected]>,
	"[email protected]" <[email protected]>,
	"[email protected]" <[email protected]>,
	"[email protected]" <[email protected]>,
	Horia Geanta <[email protected]>,
	Pankaj Gupta <[email protected]>, Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	Boris Pismenny <[email protected]>,
	John Fastabend <[email protected]>,
	Daniel Borkmann <[email protected]>,
	"[email protected]" <[email protected]>
Subject: RE: [EXT] Re: [BUG] Layerscape CAAM+kTLS+io_uring
Date: Tue, 17 May 2022 06:30:32 +0000	[thread overview]
Message-ID: <VI1PR04MB5342B4B4BC56387BB1193997E7CE9@VI1PR04MB5342.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>

Hello Steffen

> -----Original Message-----
> From: Steffen Trumtrar <[email protected]>
> Sent: Monday, May 16, 2022 3:36 PM
> To: Jakub Kicinski <[email protected]>
> Cc: Marc Kleine-Budde <[email protected]>; [email protected];
> [email protected]; [email protected]; Horia Geanta
> <[email protected]>; Pankaj Gupta <[email protected]>; Gaurav Jain
> <[email protected]>; Jens Axboe <[email protected]>; Pavel Begunkov
> <[email protected]>; Boris Pismenny <[email protected]>; John
> Fastabend <[email protected]>; Daniel Borkmann
> <[email protected]>; [email protected]
> Subject: [EXT] Re: [BUG] Layerscape CAAM+kTLS+io_uring
> 
> Caution: EXT Email
> 
> Jakub Kicinski <[email protected]> writes:
> 
> > On Thu, 5 May 2022 21:20:46 +0200 Marc Kleine-Budde wrote:
> >> Hello,
> >>
> >> no one seems to care about this problem. :/
> >>
> >> Maybe too many components are involved, I'm the respective
> >> maintainers on Cc.
> >>
> >> Cc += the CAAM maintainers
> >> Cc += the io_uring maintainers
> >> Cc += the kTLS maintainers
> >>
> >> On 27.04.2022 10:20:40, Steffen Trumtrar wrote:
> >> > Hi all,
> >> >
> >> > I have a Layerscape-1046a based board where I'm trying to use a
> >> > combination of liburing (v2.0) with splice, kTLS and CAAM (kernel
> >> > v5.17). The problem I see is that on shutdown the last bytes are
> >> > missing. It looks like io_uring is not waiting for all completions
> >> > from the CAAM driver.
> >> >
> >> > With ARM-ASM instead of the CAAM, the setup works fine.
> >>
> >> What's the difference between the CAAM and ARM-ASM crypto? Without
> >> looking into the code I think the CAAM is asynchron while ARM-ASM is
> >> synchron. Is this worth investigating?
> >
> > Sounds like
> > 20ffc7adf53a ("net/tls: missing received data after fast remote
> > close")
> 
> That fixes something in tls_sw. I have a kernel that includes this patch. So this
> sounds right, but can't be it, right?
> 
To understand more on problem, can you share how you are offloading ktls to CAAM?

Gaurav
> 
> Best regards,
> Steffen
> 
> --
> Pengutronix e.K.                | Dipl.-Inform. Steffen Trumtrar |
> Steuerwalder Str. 21            |
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pe
> ngutronix.de%2F&amp;data=05%7C01%7Cgaurav.jain%40nxp.com%7Cc225fa4
> 3da7f4a43f16b08da3723dc4a%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%
> 7C0%7C637882924400875890%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wL
> jAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C
> %7C&amp;sdata=fI1BHNZIT5RlpjEdEMXVkv1WaHcvgTlZOcaC0LRojac%3D&amp;
> reserved=0    |
> 31137 Hildesheim, Germany       | Phone: +49-5121-206917-0       |
> Amtsgericht Hildesheim, HRA 2686| Fax:   +49-5121-206917-5555    |

      reply	other threads:[~2022-05-17  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  8:20 [BUG] Layerscape CAAM+kTLS+io_uring Steffen Trumtrar
2022-05-05 19:20 ` Marc Kleine-Budde
2022-05-06  0:10   ` Jakub Kicinski
2022-05-16 10:06     ` Steffen Trumtrar
2022-05-17  6:30       ` Gaurav Jain [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=VI1PR04MB5342B4B4BC56387BB1193997E7CE9@VI1PR04MB5342.eurprd04.prod.outlook.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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