From: Miklos Szeredi <miklos@szeredi.hu>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: Bernd Schubert <bschubert@ddn.com>,
linux-fsdevel@vger.kernel.org, josef@toxicpanda.com,
joannelkoong@gmail.com
Subject: Re: [PATCH v3] fuse: Allow page aligned writes
Date: Thu, 29 Aug 2024 14:46:42 +0200 [thread overview]
Message-ID: <CAJfpegt1yY+mHWan6h_B20-i-pbmNSLEu7Fg_MsMo-cB_hFe_w@mail.gmail.com> (raw)
In-Reply-To: <a71d9bc4-fa6f-4cfd-bd96-e1001c3061fe@fastmail.fm>
On Mon, 12 Aug 2024 at 18:37, Bernd Schubert <bernd.schubert@fastmail.fm> wrote:
>
> Sorry, I had sent out the wrong/old patch file - it doesn't have one change
> (handling of already aligned buffers).
> Shall I sent v4? The correct version is below
>
> ---
>
> From: Bernd Schubert <bschubert@ddn.com>
> Date: Fri, 21 Jun 2024 11:51:23 +0200
> Subject: [PATCH v3] fuse: Allow page aligned writes
>
> Write IOs should be page aligned as fuse server
> might need to copy data to another buffer otherwise in
> order to fulfill network or device storage requirements.
Okay.
So why not align the buffer in userspace so the payload of the write
request lands on a page boundary?
Just the case that you have noted in the fuse_copy_align() function.
Thanks,
Miklos
next prev parent reply other threads:[~2024-08-29 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 16:18 [PATCH v3] fuse: Allow page aligned writes Bernd Schubert
2024-08-12 16:37 ` Bernd Schubert
2024-08-12 23:26 ` Joanne Koong
2024-08-14 16:02 ` Josef Bacik
2024-08-29 12:46 ` Miklos Szeredi [this message]
2024-08-29 13:04 ` Bernd Schubert
2024-08-29 13:06 ` Bernd Schubert
2024-08-29 13:45 ` Miklos Szeredi
2024-08-29 14:02 ` Bernd Schubert
2024-08-29 13:39 ` Miklos Szeredi
2024-09-02 20:59 ` Bernd Schubert
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=CAJfpegt1yY+mHWan6h_B20-i-pbmNSLEu7Fg_MsMo-cB_hFe_w@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=bernd.schubert@fastmail.fm \
--cc=bschubert@ddn.com \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
/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 NNTP newsgroup(s).