From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_05, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DD608C433ED for ; Tue, 6 Apr 2021 08:47:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A21C96139B for ; Tue, 6 Apr 2021 08:47:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235446AbhDFIsB (ORCPT ); Tue, 6 Apr 2021 04:48:01 -0400 Received: from ishtar.tlinx.org ([173.164.175.65]:44710 "EHLO Ishtar.sc.tlinx.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232593AbhDFIsB (ORCPT ); Tue, 6 Apr 2021 04:48:01 -0400 X-Greylist: delayed 604 seconds by postgrey-1.27 at vger.kernel.org; Tue, 06 Apr 2021 04:48:00 EDT Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id 1368bg6U037088; Tue, 6 Apr 2021 01:37:44 -0700 Message-ID: <606C1DD6.80606@tlinx.org> Date: Tue, 06 Apr 2021 01:37:42 -0700 From: "L. A. Walsh" User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Dan Carpenter CC: namjae.jeon@samsung.com, linux-cifs@vger.kernel.org Subject: cifsd: introduce SMB3 kernel server References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-cifs@vger.kernel.org On 2021/03/18 06:12, Dan Carpenter wrote: > [ cifsd: introduce SMB3 kernel server" Is it to be Linux policy that it will give in-kernel support for only for smb3, or is it planned to move the rest of the proto into the kernel as well? It sorta seems like earlier parts of the protocol, still dominant on home networks, though it seems linux not supporting all of linux's smb devices, from smb2.1 and before. I'm sure those clients would benefit as well, being kernel services could allow for a lower latency with potentially faster response time from being a kernel service instead of user-mode client? Is that also planned? Isn't the base of an smb3 server the same functions of an smb2.x server with the new smb3 extensions? Thanks!