On Thu, Apr 30, 2009 at 11:53 AM, Ted Unangst <[email protected]> wrote: > All your plans address making the crypto code faster, but I'm not sure > that's actually the slow point.
That's possible, hence the first step of benchmarking to see if it helps at all. If not, I'll take a stab at improving something else first/instead. :) > I think the crypto framework still > does too many context switches for small operations. IIRC It also > doesn't do much load balancing when you have multiple accelerators in > the system. I'm not too interested in accelerator cards at this point, just software implementations (i.e., cryptosoft.c), and my current understanding is that these are handled without context switches. Is that mistaken? (I am somewhat interested in also experimenting with using high-end graphics cards with programmable GPUs to handle offloading crypto work too, but that's a way off project, if ever; the plan I already outlined feels much more reasonable at this point.)
