Date: Mon, 21 Oct 2013 18:42:36 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John-Mark Gurney <jmg@funkthat.com> 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: <37803.1382380956@critter.freebsd.dk> In-Reply-To: <20131021183658.GY56872@funkthat.com> 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> <20131021183658.GY56872@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20131021183658.GY56872@funkthat.com>, John-Mark Gurney writes: >Poul-Henning Kamp wrote this message on Mon, Oct 21, 2013 at 18:32 +0000: >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... No, what I'm saying is that we should offer two APIs: One synchronous and one for IPSEC and any other async usage (personally I can't think of any but...) Those APIs should do whatever is fastest, for the request it gets. We do *not* want to pollute all crypto-using code with heuristics to guess which API to call for which request and when. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37803.1382380956>