From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Amir Goldstein <amir73il@gmail.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Linux kernel SMB server (CIFSD)
Date: Wed, 24 Jul 2019 14:52:26 +0900 [thread overview]
Message-ID: <20190724055226.GA15444@jagdpanzerIV> (raw)
In-Reply-To: <20190530055947.GA29812@mit.edu>
Cc-ing Jan, Amir, Jeff
Hi!
On (05/30/19 01:59), Theodore Ts'o wrote:
> From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
[..]
> 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.
To extend the topic with some discussion points:
- We are facing a rather familiar problem. Basically, SMB2 CHANGE_NOTIFY
[1] is something what fsnotify normally does, except that we can't use
it in cifsd kernel module. I see that NFS guys had [2] same issues some
time ago.
So the question is - how to do fs notify style monitoring in a kernel
module (nfsd, cifsd)? Any chance the kernel can start exporting fsnotify
symbols?
[1] https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2/598f395a-e7a2-4cc8-afb3-ccb30dd2df7c
[2] https://lore.kernel.org/linux-fsdevel/1441968882-7851-5-git-send-email-jeff.layton@primarydata.com/
-ss
next prev parent reply other threads:[~2019-07-24 5:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 5:59 Theodore Ts'o
2019-07-24 5:52 ` Sergey Senozhatsky [this message]
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=20190724055226.GA15444@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=amir73il@gmail.com \
--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