Linux-CIFS Archive mirror
 help / color / mirror / Atom feed
From: Tom Talpey <tom@talpey.com>
To: Steve French <smfrench@gmail.com>,
	"Stefan (metze) Metzmacher" <metze@samba.org>
Cc: Meetakshi Setiya <meetakshisetiyaoss@gmail.com>,
	CIFS <linux-cifs@vger.kernel.org>,
	Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: smbdirect/RDMA patches for 6.18
Date: Mon, 22 Sep 2025 14:18:47 -0400	[thread overview]
Message-ID: <5987d33c-f3dc-47a4-8ac9-befd689c0650@talpey.com> (raw)
In-Reply-To: <CAH2r5mtPs4=gUB02r12MN29kwK57+qJ_ugAsN6=83_vhA5aDCA@mail.gmail.com>

On 9/19/2025 9:57 PM, Steve French wrote:
> I have rebased the very large set of RDMA/smbdirect patches from Metze
> on current mainline from today (and the patches in ksmbd-for-next and
> for-next).
> 
> https://git.samba.org/?p=sfrench/cifs-2.6.git;a=shortlog;h=refs/heads/for-next-next;pg=1
> 
> Testing and review would be very welcome.   There was a lot of
> discussion and testing of these at the SMB3 test event at the annual
> Storage Developer Conference this week (and they look VERY promising),
> but it is a very large set, so more reviews and testing will be
> helpful.

FYI the server-side ones were tested on my machines at last week's
IOLab and they checked out well so far. They passed the relevant
WinProtocol tests as well. I need to verify some details so this
is not yet a Tested-by from me however.

I also plan to review in more detail. Thanks for merging, it makes
this easier.

Tom.

      reply	other threads:[~2025-09-22 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20  1:57 smbdirect/RDMA patches for 6.18 Steve French
2025-09-22 18:18 ` Tom Talpey [this message]

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=5987d33c-f3dc-47a4-8ac9-befd689c0650@talpey.com \
    --to=tom@talpey.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=meetakshisetiyaoss@gmail.com \
    --cc=metze@samba.org \
    --cc=smfrench@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).