According to my attempts to fix this bug, I totally disagree with you. This bug is caused by pure design of current block dev layer. Methods which are good to develop code is absolutely improper for developing ideas. It's probably the key problem of the Linux Comunity. Currently, there is merged WA for block devices with a good queue such as Samsung Pro NVMe.
WBR, Vitaly (In reply to _Vi from comment #665) > As far as I understand, this is kind of meta-bug: there are multiple causes > and multiple fixes. > > "I do bulk IO and it gets slow" sounds rather general, and problem that can > resurface anytime due to some new underlying issue. So the problem cannot be > really "closed for good" no matter how much technical progress is made. > > For me 12309 basically stopped happening unless I deliberately tune > "/proc/sys/vm/dirty_*" values to non-typical ranges and forgot to revert > them back. I see system controllably slowing down processes doing bulk IO so > the system in general stays reasonable. This behaviour is one of outcomes of > this bug. > > I don't expect meaningful technical discussion to be happen in this thread. > It should just serve as a hub for linking to specific new issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988799 Title: Precise freezes under heavy i/o To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/988799/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
