linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md: don't delay reboot by 1 second if no MD devices exist
Date: Fri, 23 Sep 2011 19:55:36 +1000	[thread overview]
Message-ID: <20110923195536.257bad23@notabene.brown> (raw)
In-Reply-To: <1316770845-18171-1-git-send-email-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

On Fri, 23 Sep 2011 10:40:45 +0100 "Daniel P. Berrange" <berrange@redhat.com>
wrote:

> From: "Daniel P. Berrange" <berrange@redhat.com>
> 
> The md_notify_reboot() method includes a call to mdelay(1000),
> to deal with "exotic SCSI devices" which are too volatile on
> reboot. The delay is unconditional. Even if the machine does
> not have any block devices, let alone MD devices, the kernel
> shutdown sequence is slowed down.
> 
> 1 second does not matter much with physical hardware, but with
> certain virtualization use cases any wasted time in the bootup
> & shutdown sequence counts for alot.
> 
> * drivers/md/md.c: md_notify_reboot() - only impose a delay if
>   there was at least one MD device to be stopped during reboot
> 
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

queued for next merge window .... or maybe even next -rc if I'm feeling
brave.

Thanks,
NeilBrown


> ---
>  drivers/md/md.c |    8 ++++++--
>  1 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 5404b22..ef7ad8d 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -8059,12 +8059,13 @@ static int md_notify_reboot(struct notifier_block *this,
>  {
>  	struct list_head *tmp;
>  	mddev_t *mddev;
> +	int need_delay = 0;
>  
>  	if ((code == SYS_DOWN) || (code == SYS_HALT) || (code == SYS_POWER_OFF)) {
>  
>  		printk(KERN_INFO "md: stopping all md devices.\n");
>  
> -		for_each_mddev(mddev, tmp)
> +		for_each_mddev(mddev, tmp) {
>  			if (mddev_trylock(mddev)) {
>  				/* Force a switch to readonly even array
>  				 * appears to still be in use.  Hence
> @@ -8073,13 +8074,16 @@ static int md_notify_reboot(struct notifier_block *this,
>  				md_set_readonly(mddev, 100);
>  				mddev_unlock(mddev);
>  			}
> +			need_delay = 1;
> +		}
>  		/*
>  		 * certain more exotic SCSI devices are known to be
>  		 * volatile wrt too early system reboots. While the
>  		 * right place to handle this issue is the given
>  		 * driver, we do want to have a safe RAID driver ...
>  		 */
> -		mdelay(1000*1);
> +		if (need_delay)
> +			mdelay(1000*1);
>  	}
>  	return NOTIFY_DONE;
>  }


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2011-09-23  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23  9:40 [PATCH] md: don't delay reboot by 1 second if no MD devices exist Daniel P. Berrange
2011-09-23  9:55 ` NeilBrown [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=20110923195536.257bad23@notabene.brown \
    --to=neilb@suse.de \
    --cc=berrange@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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).