From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Xiaoli Feng'" <xifeng@redhat.com>
Cc: "'linux-cifs'" <linux-cifs@vger.kernel.org>,
"'Tom Talpey'" <ttalpey@microsoft.com>,
<linux-cifsd-devel@lists.sourceforge.net>,
"'ronnie sahlberg'" <ronniesahlberg@gmail.com>,
"'Hyeoncheol Lee'" <hyc.lee@gmail.com>
Subject: RE: [Linux-cifsd-devel] How to use SMB Direct
Date: Thu, 19 Dec 2019 16:01:35 +0900 [thread overview]
Message-ID: <004001d5b63a$271ae4d0$7550ae70$@samsung.com> (raw)
In-Reply-To: <CANFS6bY6b23MznmrGuugcVUEW3UuRbzAxBd4p35K3qdkz4DCAA@mail.gmail.com>
Please read README file to build cifsd
And SMB direct disabled by default.
Enable smb direct support on config.
<M> CIFS server support
[*] Support for SMB Direct protocol
> -----Original Message-----
> From: Hyeoncheol Lee <hyc.lee@gmail.com>
> Sent: Thursday, December 19, 2019 3:48 PM
> To: Xiaoli Feng <xifeng@redhat.com>
> Cc: linux-cifs <linux-cifs@vger.kernel.org>; Tom Talpey
> <ttalpey@microsoft.com>; linux-cifsd-devel@lists.sourceforge.net; ronnie
> sahlberg <ronniesahlberg@gmail.com>
> Subject: Re: [Linux-cifsd-devel] How to use SMB Direct
>
> Hello Xiaoli,
>
> cifsd is an in-kernel SMB server which supports SMB Direct.
> If you want to test SMB Direct with cifs, you can use cifsd.
>
> Currently we have tested SMB Direct between two old fashioned Mellanox
> ConnectX devices which are connected directly, and between two soft RoCE
> devices in kernel.
>
> You can get cifsd's code from the following url, and If you have any
> questions, we will help you.
>
> https://protect2.fireeye.com/url?k=02be8777-5f6a3b1f-02bf0c38-
> 0cc47a3356b2-b295524a9bc31dd5&u=https://github.com/cifsd-team/cifsd.git
>
> Thank you.
>
>
> 2019년 12월 19일 (목) 오전 11:35, Xiaoli Feng <xifeng@redhat.com>님이 작성:
> >
> > Thanks Ronnie for the information. Last question: Is it supported that
> > mount the windows file server(has rdma hardware) with SMB Direct in
> linux client(has rdma hardware)?
> >
> > ----- Original Message -----
> > > From: "ronnie sahlberg" <ronniesahlberg@gmail.com>
> > > To: "Xiaoli Feng" <xifeng@redhat.com>
> > > Cc: "Tom Talpey" <ttalpey@microsoft.com>, "linux-cifs"
> > > <linux-cifs@vger.kernel.org>
> > > Sent: Wednesday, December 18, 2019 4:12:32 PM
> > > Subject: Re: How to use SMB Direct
> > >
> > > I don't think samba supports SMB Direct.
> > > Metze used to have a private repo with some experimental patches but
> > > I don't think it has landed in official samba yet.
> > >
> > > For a linux server, there is an experimental kernel based server
> > > called cifsd which should support SMBDirect but is incomplete in
> > > other areas. It is not part of linus tree yet (but soon I hope).
> > >
> > > Windows servers support SMBDirect but I am not aware of any
> > > soft-rdma support so you might be limited to just using real hw for
> > > any tests.
> > >
> > > Linux serverside SMBD support is not ready afaik.
> > >
> > > On Wed, Dec 18, 2019 at 12:49 PM Xiaoli Feng <xifeng@redhat.com> wrote:
> > > >
> > > > Hello Tom,
> > > >
> > > > Then I try to use IP to mount, it show this error:
> > > > [79912.177783] CIFS VFS: _smbd_get_connection:1740 rdma_connect
> > > > failed
> > > > port=5445
> > > > [79912.220723] CIFS VFS: _smbd_get_connection:1740 rdma_connect
> > > > failed
> > > > port=445
> > > >
> > > > Client:
> > > > $ mount //172.31.0.250/cifs cifs -o user=root,password=redhat,rdma
> > > > mount error(2): No such file or directory Refer to the
> > > > mount.cifs(8) manual page (e.g. man mount.cifs)
> > > >
> > > > Server:
> > > > $ ib addr |grep 172.31.0.250/
> > > > mlx4_ib0: Link UP, Interface UP 172.31.0.250/24
> > > >
> > > > Samba version is 4.11.2. And firewalld is stopped.
> > > >
> > > > ----- Original Message -----
> > > > > From: "Tom Talpey" <ttalpey@microsoft.com>
> > > > > To: "Xiaoli Feng" <xifeng@redhat.com>,
> > > > > linux-cifs@vger.kernel.org
> > > > > Sent: Tuesday, December 17, 2019 1:11:24 AM
> > > > > Subject: RE: How to use SMB Direct
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: linux-cifs-owner@vger.kernel.org
> > > > > > <linux-cifs-owner@vger.kernel.org>
> > > > > > On
> > > > > > Behalf Of Xiaoli Feng
> > > > > > Sent: Monday, December 16, 2019 10:30 AM
> > > > > > To: linux-cifs@vger.kernel.org
> > > > > > Subject: [EXTERNAL] How to use SMB Direct
> > > > > >
> > > > > > Hello guys,
> > > > > >
> > > > > > I'd like to test SMB Direct. But it's failed. I'm not sure if
> > > > > > it works in upstream.
> > > > > > I setup samba server on one rdma machine with 5.5.0-rc1+
> > > > > > kernel. The smb.conf is:
> > > > > > [cifs]
> > > > > > path=/mnt/cifs
> > > > > > writeable=yes
> > > > > >
> > > > > > Then I try to mount the share on another rdma machine with
> > > > > > 5.5.0-rc1+ kernel.
> > > > > > mount //$RDMA/cifs cifs -o
> > > > > > user=root,password=$password,rdma
> > > > > >
> > > > > > It's failed because of "CIFS VFS: smbd_create_id:614
> > > > > > rdma_resolve_addr()
> > > > > > completed -113"
> > > > >
> > > > > Errno 113 is "no route to host". Sounds like a network or address
> issue.
> > > > >
> > > > > Tom.
> > > > >
> > > > > > Does SMB Direct work fine in upstream?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > $ cat /boot/config-5.5.0-rc1+ |grep SMB_DIRECT
> > > > > > CONFIG_CIFS_SMB_DIRECT=y $ ibstat CA 'mlx4_0'
> > > > > > CA type: MT4099
> > > > > > Number of ports: 2
> > > > > > Firmware version: 2.42.5000
> > > > > > Hardware version: 1
> > > > > > Node GUID: 0xf4521403007be0e0
> > > > > > System image GUID: 0xf4521403007be0e3
> > > > > > Port 1:
> > > > > > State: Active
> > > > > > Physical state: LinkUp
> > > > > > Rate: 56
> > > > > > Base lid: 29
> > > > > > LMC: 0
> > > > > > SM lid: 1
> > > > > > Capability mask: 0x0259486a
> > > > > > Port GUID: 0xf4521403007be0e1
> > > > > > Link layer: InfiniBand
> > > > > > Port 2:
> > > > > > State: Active
> > > > > > Physical state: LinkUp
> > > > > > Rate: 40
> > > > > > Base lid: 44
> > > > > > LMC: 1
> > > > > > SM lid: 36
> > > > > > Capability mask: 0x02594868
> > > > > > Port GUID: 0xf4521403007be0e2
> > > > > > Link layer: InfiniBand
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best regards!
> > > > > > XiaoLi Feng 冯小丽
> > > > > >
> > > > > > Red Hat Software (Beijing) Co.,Ltd filesystem-qe Team
> > > > > > IRC:xifeng,#channel: fs-qe
> > > > > > Tel:+86-10-8388112
> > > > > > 9/F, Raycom
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>
> _______________________________________________
> Linux-cifsd-devel mailing list
> Linux-cifsd-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-cifsd-devel
next prev parent reply other threads:[~2019-12-19 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1327532317.1529923.1576509501382.JavaMail.zimbra@redhat.com>
2019-12-16 15:30 ` How to use SMB Direct Xiaoli Feng
2019-12-16 17:11 ` Tom Talpey
2019-12-18 2:48 ` Xiaoli Feng
2019-12-18 8:12 ` ronnie sahlberg
2019-12-19 2:34 ` Xiaoli Feng
2019-12-19 2:58 ` ronnie sahlberg
2019-12-19 6:47 ` Hyeoncheol Lee
2019-12-19 6:56 ` ronnie sahlberg
2019-12-19 7:48 ` Hyunchul Lee
2019-12-19 7:01 ` Namjae Jeon [this message]
2019-12-20 2:59 ` Xiaoli Feng
2019-12-20 3:26 ` Steve French
2019-12-20 13:25 ` Stefan Metzmacher
2019-12-20 4:33 ` Hyunchul Lee
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='004001d5b63a$271ae4d0$7550ae70$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=hyc.lee@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=ronniesahlberg@gmail.com \
--cc=ttalpey@microsoft.com \
--cc=xifeng@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