From: David Laight <David.Laight@ACULAB.COM>
To: 'Jakub Kicinski' <kuba@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "Alexander Aring" <aahringo@redhat.com>,
"Stefan Metzmacher" <metze@samba.org>,
"Steve French" <smfrench@gmail.com>,
"Aurélien Aptel" <aaptel@suse.com>,
"Network Development" <netdev@vger.kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
"Leif Sahlberg" <lsahlber@redhat.com>,
"Steven Whitehouse" <swhiteho@redhat.com>
Subject: RE: quic in-kernel implementation?
Date: Sun, 13 Jun 2021 12:17:45 +0000 [thread overview]
Message-ID: <166ca5b32a9d4576bc02cd8972a281e9@AcuMS.aculab.com> (raw)
In-Reply-To: <20210609094818.7aaf21bd@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
From: Jakub Kicinski
> Sent: 09 June 2021 17:48
...
> > > I think two veth interfaces can help to test something like that,
> > > either with a "fuse-like socket" on the other end or an user space
> > > application. Just doing a ping-pong example.
> > >
> > > Afterwards we can look at how to replace the user generated socket
> > > application with any $LIBQUIC e.g. msquic implementation as second
> > > step.
> >
> > Socket state management is complex and timers etc in userspace are hard.
>
> +1 seeing the struggles fuse causes in storage land "fuse for sockets"
> is not an exciting temporary solution IMHO..
Especially since you'd want reasonable performance for quic.
Fuse is normally used to access obscure filesystems where
you just need access, rather than something that really
needs to be quick.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-06-13 12:17 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 [this message]
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=166ca5b32a9d4576bc02cd8972a281e9@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=aahringo@redhat.com \
--cc=aaptel@suse.com \
--cc=kuba@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=metze@samba.org \
--cc=netdev@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stephen@networkplumber.org \
--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).