From: Pavel Machek <pavel@suse.cz>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jens Axboe <axboe@suse.de>, Jon Escombe <trial@dresco.co.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Suspend/Resume
Date: Mon, 9 May 2005 21:17:22 +0200 [thread overview]
Message-ID: <20050509191722.GB3085@elf.ucw.cz> (raw)
In-Reply-To: <1115647641.5051.1.camel@mulgrave>
On Po 09-05-05 09:07:21, James Bottomley wrote:
> On Mon, 2005-05-09 at 12:13 +0200, Pavel Machek wrote:
> > In IDE we do that to reliably flush drive caches... If write caching
> > actually works on SCSI, we should not need that hacks.
>
> Define "works". Actual write caching works fine with IDE (it doesn't
> lose the data). On the other hand, turning the cache off or flushing it
> can be problematic because not all IDE devices respond to these
> commands.
>
> So, what I think you're saying is that you don't want the internal
> drives to spin down, but you do want to send a synchronize cache command
> to those which have a writeback cache enabled?
Yes, something like that. I don't care if drivers are spinning or not,
but I need caches to be properly flushed and drive ready for system
powerdown.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
prev parent reply other threads:[~2005-05-09 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 14:16 Suspend/Resume Davy Durham
2005-05-02 14:23 ` Suspend/Resume Jon Escombe
2005-05-02 14:47 ` Suspend/Resume Jens Axboe
2005-05-02 20:13 ` Suspend/Resume Jon Escombe
2005-05-03 14:10 ` Suspend/Resume Jens Axboe
2005-05-08 3:53 ` Suspend/Resume James Bottomley
2005-05-08 16:21 ` Suspend/Resume Jens Axboe
2005-05-08 17:08 ` Suspend/Resume James Bottomley
2005-05-09 10:13 ` Suspend/Resume Pavel Machek
2005-05-09 14:07 ` Suspend/Resume James Bottomley
2005-05-09 19:17 ` Pavel Machek [this message]
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=20050509191722.GB3085@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=James.Bottomley@SteelEye.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trial@dresco.co.uk \
/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
all inboxes | Powered by JetHome®