[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 12/15] fuse: Reduce max read size
|
From: |
Stefan Hajnoczi |
|
Subject: |
Re: [PATCH 12/15] fuse: Reduce max read size |
|
Date: |
Thu, 27 Mar 2025 11:35:34 -0400 |
On Tue, Mar 25, 2025 at 05:06:52PM +0100, Hanna Czenczek wrote:
> We are going to introduce parallel processing via coroutines, a maximum
> read size of 64 MB may be problematic, allowing users of the export to
> force us to allocate quite large amounts of memory with just a few
> requests.
>
> At least tone it down to 1 MB, which is still probably far more than
> enough. (Larger requests are split automatically by the FUSE kernel
> driver anyway.)
>
> (Yes, we inadvertently already had parallel request processing due to
> nested polling before. Better to fix this late than never.)
>
> Signed-off-by: Hanna Czenczek <hreitz@redhat.com>
> ---
> block/export/fuse.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
signature.asc
Description: PGP signature
- Re: [PATCH 07/15] fuse: Set direct_io and parallel_direct_writes, (continued)
- [PATCH 15/15] fuse: Increase MAX_WRITE_SIZE with a second buffer, Hanna Czenczek, 2025/03/25
- [PATCH 08/15] fuse: Introduce fuse_{at,de}tach_handlers(), Hanna Czenczek, 2025/03/25
- [PATCH 11/15] fuse: Manually process requests (without libfuse), Hanna Czenczek, 2025/03/25
- [PATCH 01/15] fuse: Copy write buffer content before polling, Hanna Czenczek, 2025/03/25
- [PATCH 12/15] fuse: Reduce max read size, Hanna Czenczek, 2025/03/25
- Re: [PATCH 12/15] fuse: Reduce max read size,
Stefan Hajnoczi <=