From: "Aurélien Aptel" <aaptel@suse.com>
To: Alexander Ahring Oder Aring <aahringo@redhat.com>,
netdev@vger.kernel.org
Cc: 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: Mon, 07 Jun 2021 18:45:09 +0200 [thread overview]
Message-ID: <87pmwxsjxm.fsf@suse.com> (raw)
In-Reply-To: <CAK-6q+hS29yoTF4tKq+Xt3G=_PPDi9vmFVwGPmutbsQyD2i=CA@mail.gmail.com>
Alexander Ahring Oder Aring <aahringo@redhat.com> writes:
> 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.
Yes SMB can work over QUIC. It would be nice if there was an in-kernel
implementation that cifs.ko could use. Many firewall block port 445
(SMB) despite the newer version of the protocol now having encryption,
signing, etc. Using QUIC (UDP port 443) would allow for more reliable
connectivity to cloud storage like azure.
There are already multiple well-tested C QUIC implementation out there
(Microsoft one for example, has a lot of extra code annotation to allow
for deep static analysis) but I'm not sure how we would go about porting
it to linux.
https://github.com/microsoft/msquic
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next prev parent reply other threads:[~2021-06-07 16:45 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 [this message]
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
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=87pmwxsjxm.fsf@suse.com \
--to=aaptel@suse.com \
--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).