From: Jeremy Allison <jra@samba.org>
To: Steven French <sfrench@samba.org>
Cc: Xin Long <lucien.xin@gmail.com>,
samba-technical@lists.samba.org,
CIFS <linux-cifs@vger.kernel.org>,
wedsonaf@gmail.com, jra@samba.org
Subject: Re: where to get the patches for samba over quic support
Date: Tue, 22 Aug 2023 16:33:12 -0700 [thread overview]
Message-ID: <ZOVFuPKFu67gbhwd@jeremy-acer> (raw)
In-Reply-To: <1c535816-0a9c-6924-642f-508e82cd0237@samba.org>
On Tue, Aug 22, 2023 at 05:02:26PM -0500, Steven French wrote:
>I was very interested in this as well and there seems to be a logical
>use case for SMB3.1.1 mounts from the kernel client (cifs.ko) since
>multiple servers already support QUIC for SMB3.1.1 mounts (e.g.
>Windows and apparently also an embedded server that demoed at Storage
>Developer Conference last year). Key question remains how much of the
>code can stay in userspace (so only the key socket read/write code
>must be in kernel, not necessarily the connection setup). There are
>also some interesting points that the Microsoft QUIC (open source
>project in github) project guys mentioned including that for testing
>you can often do "unencrypted QUIC" as a first step (which also has
>performance benefits over TCP)
>
>We can discuss more details if you want, but Wedson had some great
>ideas about doing some of this in Rust (and looks there are already 3
>work in progress user space opensource QUIC implementations in Rust -
>so some of the code could be reused)
>
>
>On 8/21/23 09:55, Xin Long wrote:
>>Hi, Samba Team,
>>
>>I'm currently working on QUIC implementation in Linux Kernel, and thinking
>>of applying it to fs/smb for SMB over QUIC in kernel. For interoperability
>>testing, I'm looking for an existing userspace implementation for SMB over
>>QUIC in Linux.
>>
>>I heard there are already some internal patches in samba for SMB over QUIC
>>support, anyone knows where I can get it for this testing?
I just did some research, and this engine (in C) appears to be easiest
to use for Samba.
https://github.com/litespeedtech/lsquic/blob/master/docs/tutorial.rst
The tutorial shows an example being used with libevent, we could
adapt this to libtevent.
prev parent reply other threads:[~2023-08-22 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADvbK_eHYFJWL3xaZeciUMPjWXqkP_Kp3DrpP-3XPyopY1yZmg@mail.gmail.com>
2023-08-22 22:02 ` where to get the patches for samba over quic support Steven French
2023-08-22 23:33 ` Jeremy Allison [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=ZOVFuPKFu67gbhwd@jeremy-acer \
--to=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=wedsonaf@gmail.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