Deutsch English Français Italiano |
<v3mko3$c1kq$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Terje Mathisen <terje.mathisen@tmsw.no> Newsgroups: comp.arch Subject: Re: Byte Addressability And Beyond Date: Tue, 4 Jun 2024 10:54:27 +0200 Organization: A noiseless patient Spider Lines: 36 Message-ID: <v3mko3$c1kq$1@dont-email.me> References: <v0s17o$2okf4$2@dont-email.me> <v31c4r$3u28v$1@dont-email.me> <v327n3$1use$1@gal.iecc.com> <BM25O.40665$HBac.4762@fx15.iad> <v32lpv$1u25$1@gal.iecc.com> <v33bqg$9cst$11@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> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Date: Tue, 04 Jun 2024 10:54:28 +0200 (CEST) Injection-Info: dont-email.me; posting-host="e45d74333c127ce2b4dec02c1d921f24"; logging-data="394906"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/VEp99bBoj0BZWtLIEq75mIAbSDHo4+DeGneFmg12hw==" User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2 Cancel-Lock: sha1:Lan1Wzyr0EWRtB7dX/t6YeZgKpE= In-Reply-To: <20240603132227.00004e0f@yahoo.com> Bytes: 2870 Michael S wrote: > On Mon, 3 Jun 2024 08:03:53 -0000 (UTC) > Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >=20 >> On Thu, 30 May 2024 18:31:46 +0000, MitchAlsup1 wrote: >> >>> 30 years ago you could say the same thing about encryption. >> >> I don=C3=A2=E2=82=AC=E2=84=A2t think newer CPUs have been optimized fo= r encryption. Instead, >> we see newer encryption algorithms (or ways of using them) that work >> better on current CPUs. >=20 > I think moderate efficiency on CPU, not too low, but not high either, > is a requirement for (symmetric-key) cipher. Esp. when the key is > 128-bit or shorter. That's correct: CPU efficiency, primarily on the reference 32-bit platform (PentiumPro=20 200 MHz) but also on an 8-bit "smart card" implementation was one of the = key requirements for the AES competition. When a group of four programmers (including me) spent a week on CERN's=20 candidate, we were able to triple the speed, bringing it into parity=20 with the eventual winner. All the finalists were more or less the same=20 speed at this point, i.e. able to do full duplex 100 Mbit/s Ethernet=20 traffic (so around 20 MB/s) on a single thread/core. Terje --=20 - <Terje.Mathisen at tmsw.no> "almost all programming can be viewed as an exercise in caching"