21 Mar, 2014

1 commit

  • The crypto algorithm modules utilizing the crypto daemon could
    be used early when the system start up. Using module_init
    does not guarantee that the daemon's work queue is initialized
    when the cypto alorithm depending on crypto_wq starts. It is necessary
    to initialize the crypto work queue earlier at the subsystem
    init time to make sure that it is initialized
    when used.

    Signed-off-by: Tim Chen
    Signed-off-by: Herbert Xu

    Tim Chen
     

01 Nov, 2011

1 commit


04 Jan, 2011

1 commit

  • kcrypto_wq and pcrypt->wq's are used to run ciphers and may consume
    considerable amount of CPU cycles. Mark both as CPU_INTENSIVE so that
    they don't block other work items.

    As the workqueues are primarily used to burn CPU cycles, concurrency
    levels shouldn't matter much and are left at 1. A higher value may be
    beneficial and needs investigation.

    Signed-off-by: Tejun Heo
    Signed-off-by: Herbert Xu

    Tejun Heo
     

19 Feb, 2009

1 commit