On Sat, Feb 07, 2009 at 04:19:12PM +0100, Frank Seidel wrote:
> From: Frank Seidel
>
> According to kerneljanitors todo list all printk calls (beginning
> a new line) should have an according KERN_* constant.
> Those are the missing pieces here for the crypto subsystem.
>
> Signed-off-by: Frank
On Thu, Feb 05, 2009 at 05:24:51PM +0100, Geert Uytterhoeven wrote:
>
> > Well with the netlink parameters these can have variable lengths
> > depending on how many parameters the user supplies.
>
> How can this be exported to userspace?
> How does this variable length parameter passing work? Do y
Uses kcrypto_wq instead of keventd_wq in chainiv
keventd_wq has potential starvation problem, so use dedicated
kcrypto_wq instead.
Signed-off-by: Huang Ying
---
crypto/Kconfig |1 +
crypto/chainiv.c |3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
--- a/crypto/Kconfig
+++ b/c
Per-CPU cryptd thread implementation based on kcrypto_wq
Original cryptd thread implementation has scalability issue, this
patch solve the issue with a per-CPU thread implementation.
struct cryptd_queue is defined to be a per-CPU queue, which holds one
struct cryptd_cpu_queue for each CPU. In str
Use dedicated workqueue for crypto subsystem
A dedicated workqueue named kcrypto_wq is created to be used by crypto
subsystem. The system shared keventd_wq is not suitable for
encryption/decryption, because of potential starvation problem.
Signed-off-by: Huang Ying
---
crypto/Kconfig
On Fri, 2009-02-06 at 17:26 -0600, Lee Nipper wrote:
> During testing however, it seems that eseqiv_givencrypt doesn't handle a
> scatterlist
> fully for an already fragmented src. For example, a large ping (> 1460 bytes)
> going out causes a scatterlist with two entries within esp_output, but it
Andrew Morton wrote :
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 9 Feb 2009 09:12:59 -0800 (PST)
bugme-dae...@bugzilla.kernel.org wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=12680
Summary: Not having a VIA PadL
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 9 Feb 2009 09:12:59 -0800 (PST)
bugme-dae...@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12680
>
>Summary: Not having a VIA PadLock hardware incurs
