Date: Mon, 21 Oct 2013 11:36:58 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Andre Oppermann <andre@freebsd.org>, Mark R V Murray <mark@grondar.org>, freebsd-arch@freebsd.org Subject: Re: always load aesni or load it when cpu supports it Message-ID: <20131021183658.GY56872@funkthat.com> In-Reply-To: <37748.1382380333@critter.freebsd.dk> References: <20131020070022.GP56872@funkthat.com> <423D921D-6CE5-49D9-BCED-AB14EB236800@grondar.org> <20131020161634.GQ56872@funkthat.com> <5264F074.4010607@freebsd.org> <20131021164034.GU56872@funkthat.com> <37693.1382379728@critter.freebsd.dk> <20131021182834.GX56872@funkthat.com> <37748.1382380333@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote this message on Mon, Oct 21, 2013 at 18:32 +0000:
> In message <20131021182834.GX56872@funkthat.com>, John-Mark Gurney writes:
>
> >If you're on a slow system (embeded x86 or arm) that has an AES
> >accelerator, you really want to be using your accelerator than wasting
> >your cpu cycles on large blockes of AES...
>
> First, as I said in my previous email: I have still to see "distant"
> crypto accelerator do any good if you have idle CPU, even on a soekris 4801.
^^^^^^^^^
If you don't have idle cpu? Also, what about power consumption?
> If you have a real-life benchmark showing that, I'd like to see it.
>
> Second, if you want a limit, at the very least it should be MAXPHYS.
Clearly you didn't completely read my first email, so you're proposing
that we ALWAYS use software AES and never use AES-NI? At least in the
context of my email, that is what the above statement says...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131021183658.GY56872>