From: Stefan Metzmacher <metze@samba.org>
To: linux-cifs@vger.kernel.org
Cc: metze@samba.org, Steve French <smfrench@gmail.com>,
Tom Talpey <tom@talpey.com>, Long Li <longli@microsoft.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Hyunchul Lee <hyc.lee@gmail.com>,
Meetakshi Setiya <meetakshisetiyaoss@gmail.com>,
samba-technical@lists.samba.org
Subject: [PATCH v2 00/12] smb:common: introduce and use common smbdirect headers/structures (step1)
Date: Wed, 28 May 2025 18:01:29 +0200 [thread overview]
Message-ID: <cover.1748446473.git.metze@samba.org> (raw)
Hi,
in preparation of a having a common smb_direct layer I started
to move things into common header files and added the first
step in using shared structues like struct smbdirect_socket.
Currently only simple things are shared and there is no
intended behaviour change (even if I found some things
I'd like to change, but I'll defer them in order to
make the review easier).
I'll work on this the next few months in order to
unify the in kernel client and server layers
and expose the result to userspace too.
So that Samba can also use it.
v2:
- change smb_direct into smbdirect
- make usage of header files just as needed
- also introduce struct smbdirect_socket[_parameters]
as shared structures
Stefan Metzmacher (12):
smb: smbdirect: add smbdirect_pdu.h with protocol definitions
smb: client: make use of common smbdirect_pdu.h
smb: server: make use of common smbdirect_pdu.h
smb: smbdirect: add smbdirect.h with public structures
smb: client: make use of common smbdirect.h
smb: server: make use of common smbdirect.h
smb: smbdirect: add smbdirect_socket.h
smb: client: make use of common smbdirect_socket
smb: server: make use of common smbdirect_socket
smb: smbdirect: introduce smbdirect_socket_parameters
smb: client: make use of common smbdirect_socket_parameters
smb: server: make use of common smbdirect_socket_parameters
fs/smb/client/cifs_debug.c | 23 +-
fs/smb/client/smb2ops.c | 14 +-
fs/smb/client/smb2pdu.c | 17 +-
fs/smb/client/smbdirect.c | 389 +++++++++++----------
fs/smb/client/smbdirect.h | 71 +---
fs/smb/common/smbdirect/smbdirect.h | 37 ++
fs/smb/common/smbdirect/smbdirect_pdu.h | 55 +++
fs/smb/common/smbdirect/smbdirect_socket.h | 43 +++
fs/smb/server/connection.c | 4 +-
fs/smb/server/connection.h | 10 +-
fs/smb/server/smb2pdu.c | 11 +-
fs/smb/server/smb2pdu.h | 6 -
fs/smb/server/transport_rdma.c | 385 +++++++++++---------
fs/smb/server/transport_rdma.h | 41 ---
14 files changed, 613 insertions(+), 493 deletions(-)
create mode 100644 fs/smb/common/smbdirect/smbdirect.h
create mode 100644 fs/smb/common/smbdirect/smbdirect_pdu.h
create mode 100644 fs/smb/common/smbdirect/smbdirect_socket.h
--
2.34.1
next reply other threads:[~2025-05-28 16:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 16:01 Stefan Metzmacher [this message]
2025-05-28 16:01 ` [PATCH v2 01/12] smb: smbdirect: add smbdirect_pdu.h with protocol definitions Stefan Metzmacher
2025-05-28 23:28 ` Namjae Jeon
2025-05-30 19:03 ` Stefan Metzmacher
2025-05-30 19:27 ` Steve French
2025-05-30 22:29 ` Namjae Jeon
[not found] ` <CAH2r5mvQbL_R9wrFRHF9_3XwM3e-=2vK=i1uaSCk37-FZmJq9g@mail.gmail.com>
2025-06-01 0:01 ` Namjae Jeon
[not found] ` <CAH2r5mso54sXPcoJWDSU4E--XMH44wFY-cdww6_6yx5CxrFtdg@mail.gmail.com>
2025-06-01 4:59 ` Namjae Jeon
2025-06-02 1:56 ` Steve French
2025-06-02 2:19 ` Namjae Jeon
2025-06-02 22:02 ` Stefan Metzmacher
2025-06-03 6:20 ` Namjae Jeon
2025-06-03 9:06 ` Stefan Metzmacher
2025-06-03 10:55 ` Namjae Jeon
2025-05-28 16:01 ` [PATCH v2 02/12] smb: client: make use of common smbdirect_pdu.h Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 03/12] smb: server: " Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 04/12] smb: smbdirect: add smbdirect.h with public structures Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 05/12] smb: client: make use of common smbdirect.h Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 06/12] smb: server: " Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 07/12] smb: smbdirect: add smbdirect_socket.h Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 08/12] smb: client: make use of common smbdirect_socket Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 09/12] smb: server: " Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 10/12] smb: smbdirect: introduce smbdirect_socket_parameters Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 11/12] smb: client: make use of common smbdirect_socket_parameters Stefan Metzmacher
2025-05-28 16:01 ` [PATCH v2 12/12] smb: server: " Stefan Metzmacher
2025-05-29 3:33 ` [PATCH v2 00/12] smb:common: introduce and use common smbdirect headers/structures (step1) Steve French
2025-05-30 16:51 ` Steve French
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=cover.1748446473.git.metze@samba.org \
--to=metze@samba.org \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=meetakshisetiyaoss@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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