public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Force IDE cache flush on shutdown
Date: Fri, 07 May 2004 11:08:18 +1000	[thread overview]
Message-ID: <1083892097.19156.111.camel@gaston> (raw)
In-Reply-To: <200405061436.58692.bzolnier@elka.pw.edu.pl>


> > +	printk("Flushing cache: %s \n", drive->name);
> > +	ide_cacheflush_p(drive);
> > +	/* give the hardware time to finish; it may return prematurely to cheat
> > */ +	mdelay(300);
> 
> I really don't like it.
> 
> Is this delay arbitrary or you know about such devices?

Agreed... Why not standby the disk instead ? We could re-use the exact
same code path as the Power Management... At least we know that once
standby complete, we are ok (though I noticed that some proprietary
OSes still impose a half a second delay after standby and before
removing power ... broken IDE disks ...)

In fact, I'd like to kill the shutdown() callback in drivers in general
as I think it's just a special case of a PM suspend in fact. The problem
is we need once for all to fix the meaning of the "state" passed to those
callbacks. Once that's done, we can have states for restart, shutdown and
kexec (which wants devices to be put idle -> stop DMA etc...)

Ben.



  reply	other threads:[~2004-05-07  1:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06  7:04 Force IDE cache flush on shutdown Arjan van de Ven
2004-05-06  7:49 ` Christoph Hellwig
2004-05-06  7:50   ` Arjan van de Ven
2004-05-06  7:55     ` Christoph Hellwig
2004-05-06 10:46       ` Arjan van de Ven
2004-05-06 10:52         ` Christoph Hellwig
2004-05-06 11:33           ` Arjan van de Ven
2004-05-06 11:45             ` Nigel Cunningham
2004-05-06 11:45             ` Arjan van de Ven
2004-05-06 12:36             ` Bartlomiej Zolnierkiewicz
2004-05-07  1:08               ` Benjamin Herrenschmidt [this message]
2004-05-06 11:38   ` Bartlomiej Zolnierkiewicz
2004-05-07  1:09     ` Benjamin Herrenschmidt
2004-05-09  2:00   ` Pavel Machek
2004-05-06  7:58 ` Jens Axboe
2004-05-06  8:04   ` Arjan van de Ven
2004-05-06  8:05     ` Jens Axboe

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=1083892097.19156.111.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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