Deutsch English Français Italiano |
<cf98e7ba84809010306e3fdea7aa103c@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: Tue, 4 Jun 2024 17:00:33 +0000 Organization: Rocksolid Light Message-ID: <cf98e7ba84809010306e3fdea7aa103c@www.novabbs.org> References: <v0s17o$2okf4$2@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> <k6k7O.8602$7jpd.5620@fx47.iad> <v3klhp$3ugeh$1@dont-email.me> <v3mljt$c63k$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="3188370"; mail-complaints-to="usenet@i2pn2.org"; posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A"; User-Agent: Rocksolid Light X-Rslight-Site: $2y$10$N2qZhBzkpmFehWtM7DRcOewk/WEwaT8FTeX3heuNJgoU3AdEGT5OW X-Spam-Checker-Version: SpamAssassin 4.0.0 X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8 Bytes: 2400 Lines: 26 Terje Mathisen wrote: > > That logic already exists, in the form of a single thread/core > dedicated > to the job. > With 30-100 cores on a single die, it becomes very cheap to dedicate > one > of them to babysit such a process, compared to the cost of making a > custom chunk of VLSI to do the same. This is particularly true because > the logic needed in the babysitting process is mostly straight line, > with a very limited number of hard-to-predict branches. > I.e. h.264 CABAC decoding has three branches per bit decoded, at least > one of them impossible to predict or work around with clever coding. How many instructions in the then-clause and in the else-clause ?? If these are smaller than 8, My 66000 can process them without "branching" using predication. > Here it makes perfect sense to have a chunk of hw to handle the heavy > lifting. Monitoring block encryption/decryption not so much. > Terje