Hello,
On 8.10.24 18:42, Alexey Kuznetsov wrote:
[Some people who received this message don't often get email from
alexey.n.kuznet...@gmail.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hello!
if (is_data)
queue_work(ploop->wq, &
Hello!
if (is_data)
queue_work(ploop->wq, &ploop->worker);
- if (is_flush)
+ else if (is_flush)
queue_work(ploop->wq, &ploop->fsync_worker);
IMHO this looks scary. bio with FLUSH must execute flush first,
and only after completion of flush data o
On 10/4/24 09:58, Alexander Atanasov wrote:
Currently there are two workers one to handle pios,
one to handle flush (via vfs_fsync). This workers are
created unbound which means they are run whenever there is a free
CPU. When ploop sends pios (via ploop_dispatch_pios) it checks
if there are da
On 8.10.24 14:35, Andrey Zhadchenko wrote:
On 10/4/24 09:58, Alexander Atanasov wrote:
Currently there are two workers one to handle pios,
one to handle flush (via vfs_fsync). This workers are
created unbound which means they are run whenever there is a free
CPU. When ploop sends pios (via plo
