| To: | James Morris <jmorris@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Asynchronous crypto layer. |
| From: | Sam Leffler <sam@xxxxxxxxx> |
| Date: | Sat, 30 Oct 2004 23:35:28 -0700 |
| Cc: | johnpol@xxxxxxxxxxx, jamal <hadi@xxxxxxxxxx>, netdev@xxxxxxxxxxx, cryptoapi@xxxxxxxxxxxxxx, "David S. Miller" <davem@xxxxxxxxxxxxx> |
| In-reply-to: | <Xine.LNX.4.44.0410310103270.28198-100000@thoron.boston.redhat.com> |
| Organization: | Errno Consulting |
| References: | <Xine.LNX.4.44.0410310103270.28198-100000@thoron.boston.redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.8 (Macintosh/20040913) |
James Morris wrote:
On Fri, 29 Oct 2004, Sam Leffler wrote: I did a prototype scheduler (never committed) that took into account per-device performance metrics and outstanding operations. The s/w crypto driver was just part of the mix. As a result fallback on overload and using s/w crypto for small operands (where the setup overhead is too costly) just fell out. Sam |
| Previous by Date: | Re: Asynchronous crypto layer., James Morris |
|---|---|
| Next by Date: | Re: net: generic netdev_ioaddr, Pekka Enberg |
| Previous by Thread: | Re: Asynchronous crypto layer., James Morris |
| Next by Thread: | Re: Asynchronous crypto layer., Eugene Surovegin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |