Deutsch English Français Italiano |
<323761a8c1539344c56a5e17cfcce408@www.novabbs.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: mitchalsup@aol.com (MitchAlsup1) Newsgroups: comp.arch Subject: Re: Byte Addressability And Beyond Date: Mon, 3 Jun 2024 22:34:46 +0000 Organization: Rocksolid Light Message-ID: <323761a8c1539344c56a5e17cfcce408@www.novabbs.org> References: <v0s17o$2okf4$2@dont-email.me> <v34v62$ln01$1@dont-email.me> <v36bva$10k3v$2@dont-email.me> <2024May29.090435@mips.complang.tuwien.ac.at> <v38opv$1gsj2$3@dont-email.me> <v38rkd$1ha8a$1@dont-email.me> <jwvttifrysb.fsf-monnier+comp.arch@gnu.org> <f90b6e03c727b0f209d64484ec097298@www.novabbs.org> <v3jtd8$3qduu$2@dont-email.me> <20240603132227.00004e0f@yahoo.com> <k6k7O.8602$7jpd.5620@fx47.iad> <v3klhp$3ugeh$1@dont-email.me> <wnl7O.10195$Inzb.2858@fx13.iad> <v3ktnl$3vv86$1@dont-email.me> <K2n7O.29169$61Y8.18080@fx15.iad> <v3l0cs$8d0$1@dont-email.me> <20240603231511.000026a8@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="3112788"; mail-complaints-to="usenet@i2pn2.org"; posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A"; User-Agent: Rocksolid Light X-Spam-Checker-Version: SpamAssassin 4.0.0 X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8 X-Rslight-Site: $2y$10$5VY2GjEKMbnckLZVlcH0POVP1V4oO9aP.OF0eEjW2mjkfkyO9PC0G Bytes: 2645 Lines: 32 Michael S wrote: > On Mon, 3 Jun 2024 18:01:00 -0000 (UTC) > Thomas Koenig <tkoenig@netcologne.de> wrote: >> Scott Lurndal <scott@slp53.sl.home> schrieb: >> >> > Adding encryption (which of the dozen standard symmetric and >> > asymmetric cipher algoritnms?) >> >> At the moment, AES. >> >> > to a hardware device does increase complexity, and >> > thus cost at the expense of extensibility (new algorithms come along >> > periodically). The cost of verifying crypto is a bit higher as it >> > is very important to get correct when baking into gates. >> >> Seems to be fairly common these days, looking at >> https://en.wikipedia.org/wiki/AES_instruction_set . >> >> It appears that one round of AES fits fairly well into one cycle. > One/cycle throughput fits well. Even two/cycle throughput fits. > One cycle latency does not fit unless you target very low frequency. > Latency on POWER9 - 6 clocks. On majority of modern Intel and AMD cores > 3-4 clocks. On Apple M1 - 3 clocks. I agree here; You should consider encryption as smaller than an FMUL unit with about the characteristics of an FMUL. 1-cycle throughput 3-5 cycle latency.