linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-ide@vger.kernel.org
Subject: Re: when are buffers/caches flushed?
Date: Thu, 18 Aug 2005 14:12:13 +0200	[thread overview]
Message-ID: <43047B1D.9010601@imc-berlin.de> (raw)
In-Reply-To: <43047830.4060705@gmail.com>

Tejun,

>>>> How about recent kernels? Does sync() block until buffers are flushed?
>>>> How can I find out if the disk caches are actually flushed?
>>>>
>>>> I want to make sure that all data is flushed to my disk drive before 
>>>> powering down the system.
>>>
>>>  All disk caches are flushed before shutdown via the following path.
>>>
>>> kernel/sys.c::sys_reboot()
>>> kernel/drivers/base/power/shutdown.c::device_shutdown()
>>>  driver specific ->shutdown callback, for ide disks, the path is
>>> drivers/ide/ide-disk.c::ide_device_shutdown()
>>> drivers/ide/ide-disk.c::ide_cacheflush_p()
>>> drivers/ide/ide-disk.c::do_idedisk_flushcache()
>>>
>>>  And, AFAIK, sync() doesn't flush disk caches.
>>
>> How about umount?
>>
> 
> [CC'ing Bartlomiej (Hi!)]
> 
>  Hmmm, umount doesn't.  I think maybe adding cache flushing to sync and 
> umount can be helpful.

Ehm. So you're saying umount does _not_ flush the disk caches? BUT it will flush 
the the fs buffers, right?

>  And one more thing, ide-disk doesn't flush cache when shutting down. It 
> flushes only when rebooting.

How about ide-cs then? When I unregister a drive?

--
Steven

  reply	other threads:[~2005-08-18 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 10:51 when are buffers/caches flushed? Steven Scholz
2005-08-18 11:24 ` Tejun Heo
2005-08-18 11:34   ` Steven Scholz
2005-08-18 11:59     ` Tejun Heo
2005-08-18 12:12       ` Steven Scholz [this message]
2005-08-18 12:19         ` Tejun Heo
2005-08-18 12:24       ` Bartlomiej Zolnierkiewicz
2005-08-18 12:44         ` Tejun Heo
2005-08-18 13:03           ` Bartlomiej Zolnierkiewicz

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=43047B1D.9010601@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).