From: Vadim Fedorenko <vfedorenko@novek.ru>
To: Alexander Aring <aahringo@redhat.com>
Cc: netdev@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-cifs@vger.kernel.org, smfrench@gmail.com,
Leif Sahlberg <lsahlber@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: quic in-kernel implementation?
Date: Wed, 9 Jun 2021 01:27:01 +0100 [thread overview]
Message-ID: <9ce530f5-cfe7-b1d4-ede6-d88801a769ba@novek.ru> (raw)
In-Reply-To: <CAK-6q+gm0C2t50myG=qNJMOOBnM7-UjfNMHK_cyPdWY5nSudHQ@mail.gmail.com>
On 08.06.2021 22:06, Alexander Aring wrote:
> Hi Vadim,
>
> On Tue, Jun 8, 2021 at 4:59 PM Vadim Fedorenko <vfedorenko@novek.ru> wrote:
>>
>> On 07.06.2021 16:25, Alexander Ahring Oder Aring wrote:
>>> Hi,
>>>
>>> as I notice there exists several quic user space implementations, is
>>> there any interest or process of doing an in-kernel implementation? I
>>> am asking because I would like to try out quic with an in-kernel
>>> application protocol like DLM. Besides DLM I've heard that the SMB
>>> community is also interested into such implementation.
>>>
>>> - Alex
>>>
>>
>> Hi!
>> I'm working on test in-kernel implementation of quic. It's based on the
>> kernel-tls work and uses the same ULP approach to setup connection
>> configuration. It's mostly about offload crypto operations of short header
>> to kernel and use user-space implementation to deal with any other types
>> of packets. Hope to test it till the end of June with some help from
>> Jakub.
>
> Thanks, sounds interesting. Does this allow the kernel to create a quic socket?
>
Not exactly. It's based on top of UDP socket and is configured by setsockopt
like it's done for Kernel TLS implementation. The main point of this work is to
offload cryptography only without implementing special address family.
next prev parent reply other threads:[~2021-06-09 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 15:25 quic in-kernel implementation? Alexander Ahring Oder Aring
2021-06-07 16:45 ` Aurélien Aptel
2021-06-08 3:04 ` Steve French
2021-06-08 7:36 ` Stefan Metzmacher
2021-06-08 21:03 ` Alexander Aring
2021-06-08 22:33 ` Stephen Hemminger
2021-06-09 16:48 ` Jakub Kicinski
2021-06-09 18:44 ` Alexander Aring
2021-06-13 12:17 ` David Laight
2021-06-13 18:08 ` Alexander Aring
2021-06-08 21:26 ` Chuck Lever III
2021-06-07 17:29 ` Chuck Lever III
2021-06-08 20:51 ` Vadim Fedorenko
2021-06-08 21:06 ` Alexander Aring
2021-06-09 0:27 ` Vadim Fedorenko [this message]
2021-09-05 14:09 ` Eric Curtin
2021-09-05 23:38 ` Steve French
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=9ce530f5-cfe7-b1d4-ede6-d88801a769ba@novek.ru \
--to=vfedorenko@novek.ru \
--cc=aahringo@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=swhiteho@redhat.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 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).