Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Stefan Metzmacher <metze@samba.org>
To: Tom Talpey <tom@talpey.com>
Cc: Steve French <smfrench@gmail.com>, Long Li <longli@microsoft.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Hyunchul Lee <hyc.lee@gmail.com>,
	samba-technical@lists.samba.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH 1/5] smb: common: split out smb_direct related header files
Date: Tue, 27 May 2025 21:59:25 +0200	[thread overview]
Message-ID: <8afdbc0b-30f9-4e17-bd34-bc807ce3883f@samba.org> (raw)
In-Reply-To: <ace9b692-3a0d-4a47-b74b-c350a72efdf1@talpey.com>

Am 27.05.25 um 20:50 schrieb Tom Talpey:
> I love the idea. Couple of questions on the pathnames...
> 
> On 5/27/2025 12:12 PM, Stefan Metzmacher wrote:
>> This is just a start moving into a common smb_direct layer.
>>
>> Cc: Steve French <smfrench@gmail.com>
>> Cc: Tom Talpey <tom@talpey.com>
>> Cc: Long Li <longli@microsoft.com>
>> Cc: Namjae Jeon <linkinjeon@kernel.org>
>> Cc: Hyunchul Lee <hyc.lee@gmail.com>
>> Cc: linux-cifs@vger.kernel.org
>> Cc: samba-technical@lists.samba.org
>> Signed-off-by: Stefan Metzmacher <metze@samba.org>
>> ---
>>   fs/smb/common/smb_direct/smb_direct.h     | 11 +++++
>>   fs/smb/common/smb_direct/smb_direct_pdu.h | 51 +++++++++++++++++++++++
> 
> Why the underscore in "smb_direct", in both components? The protocol
> doesn't use this, and it seems awkward and search-unfriendly.

Yes, I'd also prefer smbdirect and I just used it because I had
my existing wip driver under that name, but that should not matter.

The other reason was that the existing structures used smb_direct_
as prefix, but I'll also change that.

>>   fs/smb/server/transport_rdma.h            | 43 +------------------
>>   3 files changed, 64 insertions(+), 41 deletions(-)
>>   create mode 100644 fs/smb/common/smb_direct/smb_direct.h
>>   create mode 100644 fs/smb/common/smb_direct/smb_direct_pdu.h
>>
>> diff --git a/fs/smb/common/smb_direct/smb_direct.h b/fs/smb/common/smb_direct/smb_direct.h
>> new file mode 100644
>> index 000000000000..c745c37a3fea
>> --- /dev/null
>> +++ b/fs/smb/common/smb_direct/smb_direct.h
>> @@ -0,0 +1,11 @@
>> +/* SPDX-License-Identifier: GPL-2.0-or-later */
>> +/*
>> + *   Copyright (C) 2025, Stefan Metzmacher <metze@samba.org>
>> + */
>> +
>> +#ifndef __FS_SMB_COMMON_SMB_DIRECT_SMB_DIRECT_H__
>> +#define __FS_SMB_COMMON_SMB_DIRECT_SMB_DIRECT_H__
>> +
>> +#include "smb_direct_pdu.h"
> 
> And, why the empty redirection? It seems unnecessary, do I assume it
> will later contain API signatures for the planned common layer? Perhaps
> it should say this, to avoid confusion while that work is being done.

I'll think about it maybe I'll remove the redirection.

In the end the pdu definitions belong only in a single common .c files,
but it will take a lot of steps to get there.

I'll post a v2 tomorrow or next week.

Thanks!
metze


  parent reply	other threads:[~2025-05-27 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 16:12 [PATCH 0/5] smb:common: introduce and use common smb_direct headers (step1) Stefan Metzmacher
2025-05-27 16:12 ` [PATCH 1/5] smb: common: split out smb_direct related header files Stefan Metzmacher
2025-05-27 18:50   ` Tom Talpey
2025-05-27 19:14     ` Steve French
2025-05-27 19:59     ` Stefan Metzmacher [this message]
2025-05-27 16:12 ` [PATCH 2/5] smb: client: make use of common smb_direct headers Stefan Metzmacher
2025-05-27 16:13 ` [PATCH 3/5] smb: common: add smb_direct_buffer_descriptor_v1 Stefan Metzmacher
2025-05-27 16:13 ` [PATCH 4/5] smb: client: make use of common smb_direct_buffer_descriptor_v1 Stefan Metzmacher
2025-05-27 16:13 ` [PATCH 5/5] smb: server: " Stefan Metzmacher

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=8afdbc0b-30f9-4e17-bd34-bc807ce3883f@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=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