| Deutsch English Français Italiano |
|
<vvtt4d$1b8s7$4@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!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro <ldo@nz.invalid> Newsgroups: comp.arch Subject: Re: Is Parallel Programming Hard, And, If So, What Can You Do About It? Date: Mon, 12 May 2025 22:35:57 -0000 (UTC) Organization: A noiseless patient Spider Lines: 20 Message-ID: <vvtt4d$1b8s7$4@dont-email.me> References: <vvnds6$3gism$1@dont-email.me> <edb59b7854474033c748f0fd668badaa@www.novabbs.org> <w32UP.481123$C51b.217868@fx17.iad> <vvqdas$g9oh$1@dont-email.me> <vvrcs9$msmc$2@dont-email.me> <0ec5d195f4732e6c92da77b7e2fa986d@www.novabbs.org> <vvribg$npn4$1@dont-email.me> <vvs343$ulkk$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 13 May 2025 00:35:57 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0448815ddbe5764c8b0618fa4f88d963"; logging-data="1418119"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Wntu0P/92Z2m7VkLmTzjg" User-Agent: Pan/0.162 (Pokrosvk) Cancel-Lock: sha1:ZFmebEShohaJ+qEDQ/n6/iRihZI= Bytes: 2112 On Mon, 12 May 2025 08:05:56 +0200, Terje Mathisen wrote: > Lawrence D'Oliveiro wrote: >> >> One of my pet peeves is disk drives with memory caches in them. Why? >> > For reads it allows the disk to always read full sets of sectors, the > following blocks are likely to be needed soon anyway. Leave that up to the OS I/O optimization algorithms. Because they know things about the data that the drive doesn’t. > For writes, as long as the drive has enough energy (maybe in the form of > spinning inertia, or a hefty cap?) the always be able to save the buffer > cache to spinning rust, it can allow operations to complete immediately, > or as soon as the data has been transferred into the disk cache. In other words, telling lies to the OS that the write has completed when it hasn’t. This kind of thing can really stuff up filesystem integrity guarantees.