Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: hehuiwen <huiwen.he@linux.dev>
To: Steve French <smfrench@gmail.com>
Cc: linkinjeon@kernel.org, pc@manguebit.org,
	ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
	bharathsm@microsoft.com, dhowells@redhat.com, metze@samba.org,
	chenxiaosong@kylinos.cn, linux-cifs@vger.kernel.org
Subject: Re: [PATCH v6 2/5] smb/client: reduce fallocate zero buffer allocation
Date: Thu, 2 Jul 2026 09:54:25 +0800	[thread overview]
Message-ID: <ec6b4552-618d-41cf-a262-0c14ebd354df@linux.dev> (raw)
In-Reply-To: <CAH2r5msyi5nvObkx+JUP78DKdthQLR4p+sg61SEW0RXATorcLg@mail.gmail.com>

Hi steve,

The normal write path can use larger writes, and dd is a good example of
that. But this patch is only changing the fallocate zero-write emulation
helper.

That helper already capped each SMB2_write to SMB2_MAX_BUFFER_SIZE 
before this patch:

        if (io_parms.length > SMB2_MAX_BUFFER_SIZE)
                io_parms.length = SMB2_MAX_BUFFER_SIZE;

So this patch does not reduce the write size on the wire. It only avoids
allocating a 1 MiB zero buffer when the current helper sends at most 64 
KiB per write.

Using the negotiated wsize here could be a useful performance 
optimization, but it needs more care to make sure the larger
write path is handled safely.

Thanks,
Huiwen

在 2026/7/2 05:44, Steve French 写道:
> Won't this hurt performance since for most servers the default max
> write size is 4MB (e.g. Samba or Windows) or 1MB?  I did a quick
> experiment with
> "dd" and I see the 4MB writes over the wire not 64K
> 
> On Wed, Jul 1, 2026 at 10:22 AM Huiwen He <huiwen.he@linux.dev> wrote:
>>
>> From: Huiwen He <hehuiwen@kylinos.cn>
>>
>> The fallocate emulation allocates a 1 MiB zero-filled buffer even
>> though each SMB2_write request is limited to SMB2_MAX_BUFFER_SIZE,
>> which is 64 KiB. A high-order 1 MiB allocation is more likely to
>> fail on a fragmented system.
>>
>> Allocate only the smaller of the requested range and SMB2_MAX_BUFFER_SIZE,
>> and reuse that zero-filled buffer for every write request. Also reject
>> a successful write that makes no progress to avoid looping indefinitely.
>>
>> This reduces the contiguous allocation required by fallocate emulation
>> without changing the written data or range semantics.
>>
>> Signed-off-by: Huiwen He <hehuiwen@kylinos.cn>
>> Reviewed-by: ChenXiaoSong <chenxiaosong@kylinos.cn>
>> ---
>>   fs/smb/client/smb2ops.c | 7 ++++---
>>   1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/smb/client/smb2ops.c b/fs/smb/client/smb2ops.c
>> index cc8e0595e504..23505ae9bd81 100644
>> --- a/fs/smb/client/smb2ops.c
>> +++ b/fs/smb/client/smb2ops.c
>> @@ -3559,7 +3559,7 @@ static int smb3_simple_fallocate_write_range(unsigned int xid,
>>                                               char *buf)
>>   {
>>          struct cifs_io_parms io_parms = {0};
>> -       int nbytes;
>> +       unsigned int nbytes;
>>          int rc = 0;
>>          struct kvec iov[2];
>>
>> @@ -3580,9 +3580,10 @@ static int smb3_simple_fallocate_write_range(unsigned int xid,
>>                  rc = SMB2_write(xid, &io_parms, &nbytes, iov, 1);
>>                  if (rc)
>>                          break;
>> +               if (!nbytes)
>> +                       return -EIO;
>>                  if (nbytes > len)
>>                          return -EINVAL;
>> -               buf += nbytes;
>>                  off += nbytes;
>>                  len -= nbytes;
>>          }
>> @@ -3611,7 +3612,7 @@ static int smb3_simple_fallocate_range(unsigned int xid,
>>          if (rc)
>>                  goto out;
>>
>> -       buf = kzalloc(1024 * 1024, GFP_KERNEL);
>> +       buf = kzalloc(min_t(loff_t, len, SMB2_MAX_BUFFER_SIZE), GFP_KERNEL);
>>          if (buf == NULL) {
>>                  rc = -ENOMEM;
>>                  goto out;
>> --
>> 2.43.0
>>
> 
> 


  reply	other threads:[~2026-07-02  1:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 15:21 [PATCH v6 0/5] smb: fix fallocate and allocation accounting Huiwen He
2026-07-01 15:21 ` [PATCH v6 1/5] smb/client: refresh allocation size after duplicate extents Huiwen He
2026-07-01 21:47   ` Steve French
2026-07-02 15:20     ` hehuiwen
2026-07-01 15:21 ` [PATCH v6 2/5] smb/client: reduce fallocate zero buffer allocation Huiwen He
2026-07-01 21:44   ` Steve French
2026-07-02  1:54     ` hehuiwen [this message]
2026-07-01 15:21 ` [PATCH v6 3/5] smb/client: emulate small EOF-extending mode 0 fallocate ranges Huiwen He
2026-07-01 15:21 ` [PATCH v6 4/5] smb/client: refresh allocation after EOF-extending fallocate Huiwen He
2026-07-01 21:19   ` Steve French
2026-07-02  3:21     ` hehuiwen
2026-07-01 15:21 ` [PATCH v6 5/5] smb/server: map SET_INFO ENOSPC to disk full Huiwen He
2026-07-02  0:21   ` Namjae Jeon

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=ec6b4552-618d-41cf-a262-0c14ebd354df@linux.dev \
    --to=huiwen.he@linux.dev \
    --cc=bharathsm@microsoft.com \
    --cc=chenxiaosong@kylinos.cn \
    --cc=dhowells@redhat.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=metze@samba.org \
    --cc=pc@manguebit.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=smfrench@gmail.com \
    --cc=sprasad@microsoft.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