calling updateParams here lead to making an api call with the default
timespan (last 3 days) on pbs/pmg when going to the 'administration'
panel, even though it would never be shown since on tab activate we would
show the 'live mode' which does not use the timespan
on pve this did not happen since
There were quite a few reports in the community forum about Windows
VMs with SATA disks not working after upgrading to kernel 5.13.
Issue was reproducible during the installation of Win2019 (suggested
by Thomas), and it's already fixed in 5.15. Bisecting led to
io-wq: split bounded and unbounde
NOTE: These changes are already included in the previous patch.
Changes to make the patches apply and compile and hopefully still be
semantically equivalent to the fix.
IRQ-safe locks were not needed anymore at some point upstream, but we
still have them.
The function io_wq_max_workers is only p
if the total we got was bigger than the last line number, we appended
empty lines at the end of the panel, to which we scrolled
the only time we need to do that is when we do not follow the task log
'live' but when we are elsewhere (to keep the scroll position/size)
so give the lines directly to
by updating the start to 'total-limit' if we follow the task log live.
to do that, we decouple the 'scroll' event from updating the 'start'
parameter and call that directly after we scrolled down.
to not trigger the scroll event multiple times, suspend the scroll event
while doing that.
while we'
improves the handling of fast moving tasks
* no glitching
* catching up to the end of the task log
changes from v1:
* dropped 3/3 (different approach makes it obsolete)
* set the length to total when we really need it
* decouple updating the start parameter from the scrollevent
* make the scrollin
On 23.11.21 12:59, Fabian Ebner wrote:
> There were quite a few reports in the community forum about Windows
> VMs with SATA disks not working after upgrading to kernel 5.13.
> Issue was reproducible during the installation of Win2019 (suggested
> by Thomas), and it's already fixed in 5.15. Bisecti
