From: "Theodore Ts'o" <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [TECH TOPIC] Linux kernel SMB server (CIFSD)
Date: Thu, 30 May 2019 01:59:47 -0400 [thread overview]
Message-ID: <20190530055947.GA29812@mit.edu> (raw)
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
[ Note: The following abstract was submitted via the Linsux Plumbers
Conference website. Per the instructions that were posted for the
Maintainer's / Kernel Summit Call for Proposals[1], the proposal
should also be posted on the ksummit-discuss list, so that people
can comment on the proposal, and perhaps start a discussion before
the summit.
[1] https://lwn.net/Articles/788378/
Please note that topic proposals for both the Kernel Summit and the
Maintainer's Summit are still welcome, and the deadline has been
extended to June 3rd. -- Ted ]
CIFSD is a new SMB server implementation for the Linux kernel
(out of tree, as of this moment), intended to be minimalistic,
yet providing better performance than user-space analogues.
This talk will briefly introduce CIFSD, its architecture (high
level) and its main design goals: outline components, their
responsibilities and communication protocols.
The work is still in progress, we are in pretty early stages,
so in the second part of the talk we will focus on current state
of affairs and our future development plans - we are looking at
possibility to merge CIFSD with the upstream Linux kernel,
sometime in the future.
next reply other threads:[~2019-05-30 5:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 5:59 Theodore Ts'o [this message]
2019-07-24 5:52 ` [Ksummit-discuss] [TECH TOPIC] Linux kernel SMB server (CIFSD) Sergey Senozhatsky
2019-07-24 8:03 ` Sergey Senozhatsky
2019-07-24 10:50 ` Amir Goldstein
2019-07-24 10:55 ` Jeff Layton
2019-07-25 5:00 ` Sergey Senozhatsky
2019-07-30 17:01 ` Jan Kara
2019-07-31 3:09 ` Sergey Senozhatsky
2019-07-30 16:55 ` Jan Kara
2019-07-24 11:28 ` Sergey Senozhatsky
2019-07-24 16:42 ` Al Viro
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=20190530055947.GA29812@mit.edu \
--to=tytso@mit.edu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).