* Re: [PATCH] fuse: disable default bdi strictlimiting [not found] ` <CAJnrk1bx+32Tq5DOk6=C+_smV2HgP3+RT6gpYLSNMEirFs_EkQ@mail.gmail.com> @ 2026-05-08 9:42 ` Miklos Szeredi 2026-05-08 11:54 ` Horst Birthelmer 0 siblings, 1 reply; 2+ messages in thread From: Miklos Szeredi @ 2026-05-08 9:42 UTC (permalink / raw) To: Joanne Koong; +Cc: linux-fsdevel, kernel-team, fuse-devel On Mon, 27 Oct 2025 at 23:39, Joanne Koong <joannelkoong@gmail.com> wrote: > Miklos, could you share your thoughts on this? Are you in favor of > disabling default strictlimiting? Or do you prefer to have it kept > enabled by default, with some mount option or sysctl added for > privileged servers to be able to disable strictlimiting + enable large > folios if they use the writeback cache? So what I think we should do is implement some sort of slow writer test, and see what happens with and without strictlimit. Tried to ask claude to do this for me, but not getting very far. So if I take this maintainership role seriously and not let myself drown in the details, then the logical thing to do is to delegate ;) Which is hard (for me at least) but I'll give it a try... Could you please check how things change if there's limited writeback rate and we disable strictlimit? And what happens if there are several such instances running in parallel? Thanks, Miklos ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Re: [PATCH] fuse: disable default bdi strictlimiting 2026-05-08 9:42 ` [PATCH] fuse: disable default bdi strictlimiting Miklos Szeredi @ 2026-05-08 11:54 ` Horst Birthelmer 0 siblings, 0 replies; 2+ messages in thread From: Horst Birthelmer @ 2026-05-08 11:54 UTC (permalink / raw) To: Miklos Szeredi; +Cc: Joanne Koong, linux-fsdevel, kernel-team, fuse-devel On Fri, May 08, 2026 at 11:42:10AM +0200, Miklos Szeredi wrote: > On Mon, 27 Oct 2025 at 23:39, Joanne Koong <joannelkoong@gmail.com> wrote: > > Miklos, could you share your thoughts on this? Are you in favor of > > disabling default strictlimiting? Or do you prefer to have it kept > > enabled by default, with some mount option or sysctl added for > > privileged servers to be able to disable strictlimiting + enable large > > folios if they use the writeback cache? > > So what I think we should do is implement some sort of slow writer > test, and see what happens with and without strictlimit. > > Tried to ask claude to do this for me, but not getting very far. > > So if I take this maintainership role seriously and not let myself > drown in the details, then the logical thing to do is to delegate ;) > Which is hard (for me at least) but I'll give it a try... > > Could you please check how things change if there's limited writeback > rate and we disable strictlimit? And what happens if there are > several such instances running in parallel? We have run all kinds of workloads and tests (xfstest, too) with writeback enabled and strictlimiting off. I have not noticed any problems, but we have not done any systematic tests regarding this. We were always testing something else. (usually performance impacts) Thanks, Horst ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-05-08 12:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20251008204133.2781356-1-joannelkoong@gmail.com>
[not found] ` <CAJfpegsyHmSAYP04ot8neu_QtsCkTA2-qc2vvvLrsNLQt1aJCg@mail.gmail.com>
[not found] ` <CAJnrk1anOVeNyzEe37p5H-z5UoKeccVMGBCUL_4pqzc=e2J7Ug@mail.gmail.com>
[not found] ` <CAJnrk1bx+32Tq5DOk6=C+_smV2HgP3+RT6gpYLSNMEirFs_EkQ@mail.gmail.com>
2026-05-08 9:42 ` [PATCH] fuse: disable default bdi strictlimiting Miklos Szeredi
2026-05-08 11:54 ` Horst Birthelmer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox