[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJfpegvTm-qniu8OOY2Riy-0xFg2=wy3ROOcrLkQ2hcZCzKgMw@mail.gmail.com>
Date: Mon, 7 Oct 2024 14:35:33 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: yangyun <yangyun50@...wei.com>
Cc: jefflexu@...ux.alibaba.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, lixiaokeng@...wei.com
Subject: Re: [PATCH] fuse: remove useless IOCB_DIRECT in fuse_direct_read/write_iter
On Tue, 27 Aug 2024 at 13:53, yangyun <yangyun50@...wei.com> wrote:
>
> On Tue, Aug 27, 2024 at 04:30:04PM +0800, Jingbo Xu wrote:
> > When the size of the user requested IO is greater than max_read and
> > max_pages constraint, it's split into multiple requests and these split
> > requests can not be sent to the fuse server until the previous split
> > request *completes* (since fuse_simple_request()), even when the user
> > request is submitted from async IO e.g. io-uring.
>
> The same use case. Your explanation is more explicit.
Applied, thanks.
Miklos
Powered by blists - more mailing lists