[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKaoeS1Ykr9E0URiasMy9j0Jw6R7AbXLbSgMV=KHyfrCakp48w@mail.gmail.com>
Date: Fri, 23 Jan 2026 11:05:26 -0800
From: Rishikesh Jethwani <rjethwani@...estorage.com>
To: Tariq Toukan <ttoukan.linux@...il.com>
Cc: netdev@...r.kernel.org, saeedm@...dia.com, tariqt@...dia.com,
mbloch@...dia.com, borisp@...dia.com, john.fastabend@...il.com,
kuba@...nel.org, sd@...asysnail.net, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, leon@...nel.org
Subject: Re: [PATCH v4 0/3] tls: Add TLS 1.3 hardware offload support
On Thu, Jan 22, 2026 at 11:22 AM Rishikesh Jethwani
<rjethwani@...estorage.com> wrote:
>
> > Hi Rishikesh,
> >
> > This version doesn't compile for us.
> > A few comments that we wanted to share on V3, but I'll share here as
> > this is the latest:
> >
> > We tested V3 and a few issues were spotted.
> > We did not debug them though...
> >
> > We run a server/client test with nginx and wrk.
> >
> > a.
> > When requesting 128-bit key, ss output shows "cipher: aes-gcm-256" for
> > the respective connection.
> > For TLS 1.2 it works fine.
> >
> > b.
> > On the wrk side, the mlx5 rx_tls_ctx did not increase (meaning no
> > offloaded connections were opened). It works fine on the nginx side
> > however...
> > For TLS 1.2 it works fine.
> >
> > We can share more info if needed.
> >
> > Regards,
> > Tariq
> >
> Hi Tariq,
>
> I have fixed the typo leading to compile errors in V5.
> Could you please share more info. about the setup and test, so that I
> can try to reproduce the issue?
>
> Thanks,
> Rishikesh
HI Tariq,
Did you run SW TLS 1.3 in your environment?
Powered by blists - more mailing lists