lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 25 May 2022 11:52:53 +0200
From:   Vincent Guittot <>
To:     Linus Walleij <>
Cc:     Allen Pais <>,
        Arnd Bergmann <>,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Subject: Re: [RFC 1/1] drivers/dma/*: replace tasklets with workqueue

On Wed, 25 May 2022 at 11:24, Linus Walleij <> wrote:
> On Tue, Apr 19, 2022 at 11:17 PM Allen Pais <> wrote:
> > The tasklet is an old API which will be deprecated, workqueue API
> > cab be used instead of them.
> >
> > This patch replaces the tasklet usage in drivers/dma/* with a
> > simple work.
> >
> > Github:
> >
> > Signed-off-by: Allen Pais <>
> Paging Vincent Guittot and Arnd Bergmann on the following question
> on this patch set:
> - Will replacing tasklets with workque like this negatively impact the
>   performance on DMA engine bottom halves?

workqueue uses cfs thread so they will be scheduled like any other
thread. Furthermore, schedule_work uses the default system workqueue
which is shared with a lot of other stuff and doesn't parallel work so
you can expect some performance impact.
If you really want to use workqueue, you should at least create your
own workqueue. But you should also have a look at irq_work; An example
of usage is kernel/sched/sched_cpufrequtil.c

> For reference:
> Yours,
> Linus Walleij

Powered by blists - more mailing lists