linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: "Lincoln Dale \(ltd\)" <ltd@cisco.com>
Cc: "Eric D. Mudama" <edmudama@gmail.com>,
	"Robert Hancock" <hancockr@shaw.ca>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Disk write cache (Was: Hyper-Threading Vulnerability)
Date: Wed, 18 May 2005 09:48:42 -0400	[thread overview]
Message-ID: <17035.18362.972972.148543@smtp.charter.net> (raw)
In-Reply-To: <26A66BC731DAB741837AF6B2E29C10171E5590@xmb-hkg-413.apac.cisco.com>

>>>>> "Lincoln" == Lincoln Dale \(ltd\) <Lincoln> writes:

Lincoln> why don't drive vendors create firmware which reserved a
Lincoln> cache-sized (e.g. 2MB) hole of internal drive space somewhere
Lincoln> for such an event, and a "cache flush caused by hard-reset"
Lincoln> simply caused it to write the cache to a fixed (contiguous)
Lincoln> area of disk.

Well, if you're losing power in the next Xmilliseconds, do you have
the time to seek to the cache holding area and settle down the head
(since you could have done a seek from the edge of the disk to the
middle), start writing, etc?  Seems better to have a cache sized flash
ram instead where you could just keep the data there in case of power
loss.  

But that's expensive, and not something most people need...

John

  reply	other threads:[~2005-05-18 13:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  9:45 Disk write cache (Was: Hyper-Threading Vulnerability) Lincoln Dale (ltd)
2005-05-18 13:48 ` John Stoffel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-18 22:11 Lincoln Dale (ltd)
2005-05-18  7:16 Paul Zimmerman
2005-05-18 11:10 ` Richard B. Johnson
2005-05-18 12:47 ` Stephan Wonczak
     [not found] <43Bnu-Ut-9@gated-at.bofh.it>
     [not found] ` <44sLm-3Mg-33@gated-at.bofh.it>
     [not found]   ` <44sUX-42h-11@gated-at.bofh.it>
     [not found]     ` <44teb-4fb-1@gated-at.bofh.it>
     [not found]       ` <44uaj-4Z3-5@gated-at.bofh.it>
     [not found]         ` <44LXu-2W6-15@gated-at.bofh.it>
     [not found]           ` <44OVj-5xS-3@gated-at.bofh.it>
     [not found]             ` <44PRr-6mz-33@gated-at.bofh.it>
2005-05-17  3:29               ` Robert Hancock
2005-05-18  4:11                 ` Eric D. Mudama
2005-05-13  5:51 Hyper-Threading Vulnerability Gabor MICSKO
2005-05-13 18:03 ` Andi Kleen
2005-05-13 19:16   ` Diego Calleja
2005-05-15  9:54     ` Andi Kleen
2005-05-15 13:51       ` Mikulas Patocka
2005-05-15 14:12         ` Andi Kleen
2005-05-15 14:52           ` Tomasz Torcz
2005-05-15 15:00             ` Disk write cache (Was: Hyper-Threading Vulnerability) Mikulas Patocka
2005-05-15 15:21               ` Gene Heskett
2005-05-15 15:29                 ` Jeff Garzik
2005-05-16  1:56                   ` Gene Heskett
2005-05-16  2:11                     ` Jeff Garzik
2005-05-16  2:24                     ` Mikulas Patocka
2005-05-16  3:05                       ` Gene Heskett
2005-05-16  2:32                     ` Mark Lord
2005-05-16  3:08                       ` Gene Heskett
2005-05-16 13:44                         ` Mark Lord
2005-05-18  4:03                       ` Eric D. Mudama
2005-05-15 16:24                 ` Mikulas Patocka
2005-05-16 11:18                   ` Matthias Andree
2005-05-16 14:33                     ` Jeff Garzik
2005-05-16 15:26                       ` Richard B. Johnson
2005-05-16 18:11                       ` Valdis.Kletnieks
2005-05-16 14:54                     ` Alan Cox
2005-05-17 13:15                       ` Bill Davidsen
2005-05-17 21:41                         ` Kyle Moffett
2005-05-18  4:06                     ` Eric D. Mudama
2005-05-15 21:38                 ` Tomasz Torcz
2005-05-16 14:50               ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17035.18362.972972.148543@smtp.charter.net \
    --to=john@stoffel.org \
    --cc=edmudama@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltd@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).