[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Let's talk about HTTPS Everywhere



Celejar:
> On Mon, 24 Jan 2011 22:33:28 +0100
> Jochen Schulz <ml@well-adjusted.de> wrote:
> 
>> Celejar:
>>> 
>>> I understand that you're technically adding traffic and processor
>>> overhead; the question is how much?
>> 
>> My 1.66GHz atom D510 can encrypt/decrypt AES with ~20MByte/s on a single
>> core. Typically, my wifi reaches only 10% of that throughput.
>> Additionally, encryption is usually done by the network adapter in
>> hardware, as far as I know. The host CPU shouldn't be stressed by that.
> 
> Thanks. What's the CPU usage like while doing AES on 20Mb?

A single core get's used 100% by the kworker thread. But actually it's
not 20MB/s, but 25MB/s while reading (decrypting) and 35MB/s while
writing (encrypting). I just tested it again.

J.
-- 
At night I go to the kitchen; specifically, the knife drawer.
[Agree]   [Disagree]
                 <http://www.slowlydownward.com/NODATA/data_enter2.html>

Attachment: signature.asc
Description: Digital signature


Reply to: