public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <linux-kernel@borntraeger.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, Hannes Reinecke <hare@suse.de>,
	linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] Limit number of concurrent hotplug processes
Date: Mon, 26 Jul 2004 08:19:36 +0200	[thread overview]
Message-ID: <200407260819.36739.linux-kernel@borntraeger.net> (raw)
In-Reply-To: <20040725182006.6c6a36df.akpm@osdl.org>

Andrew Morton wrote:
> Hannes Reinecke <hare@suse.de> wrote:
> > the attached patch limits the number of concurrent hotplug processes.

> hm, it's a bit sad that this happens.  Are you able to tell us more about
> what is causing such an explosion of module probes?

I dont know exactly which scenario Hannes has seen, but its quite simple to 
trigger this scenario with almost any s390/zSeries.

Using the Hardware Management Console or z/VM you are able to hotplug 
(deactive/activate/attach/detach) almost every channel path. As a channel 
path can connect a big bunch of devices lots of machine checks are 
triggered, which causes lots of hotplugs. The same amount of machine checks 
could happen if a hardware failure happens. 

Some month ago I played around with a diet version of  hotplug. This program 
was fast and small enough to make my scenario work properly. Nevertheless, 
as hannes already stated this will only delay the problem. 

cheers

Christian


  reply	other threads:[~2004-07-26  6:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 13:52 [PATCH] Limit number of concurrent hotplug processes Hannes Reinecke
2004-07-26  1:20 ` Andrew Morton
2004-07-26  6:19   ` Christian Borntraeger [this message]
2004-07-26 10:59   ` Hannes Reinecke
2004-07-26 20:18     ` Andrew Morton
2004-07-27  7:04       ` Hannes Reinecke
2004-07-27  7:24         ` Andrew Morton
2004-07-27  7:59           ` Hannes Reinecke
2004-07-27  8:34             ` Andrew Morton
2004-07-27  9:05               ` Hannes Reinecke
2004-07-27  9:28                 ` Andrew Morton
2004-07-27 12:22                   ` Hannes Reinecke
2004-07-28  7:12                   ` Paul Jackson

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=200407260819.36739.linux-kernel@borntraeger.net \
    --to=linux-kernel@borntraeger.net \
    --cc=akpm@osdl.org \
    --cc=hare@suse.de \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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