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 06:19:36 +0000 [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
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
WARNING: multiple messages have this Message-ID (diff)
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
next prev parent reply other threads:[~2004-07-26 6:19 UTC|newest]
Thread overview: 26+ 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-20 13:52 ` Hannes Reinecke
2004-07-26 1:20 ` Andrew Morton
2004-07-26 1:20 ` Andrew Morton
2004-07-26 6:19 ` Christian Borntraeger [this message]
2004-07-26 6:19 ` Christian Borntraeger
2004-07-26 10:59 ` Hannes Reinecke
2004-07-26 10:59 ` Hannes Reinecke
2004-07-26 20:18 ` Andrew Morton
2004-07-26 20:18 ` Andrew Morton
2004-07-27 7:04 ` Hannes Reinecke
2004-07-27 7:04 ` Hannes Reinecke
2004-07-27 7:24 ` Andrew Morton
2004-07-27 7:24 ` Andrew Morton
2004-07-27 7:59 ` Hannes Reinecke
2004-07-27 7:59 ` Hannes Reinecke
2004-07-27 8:34 ` Andrew Morton
2004-07-27 8:34 ` Andrew Morton
2004-07-27 9:05 ` Hannes Reinecke
2004-07-27 9:05 ` Hannes Reinecke
2004-07-27 9:28 ` Andrew Morton
2004-07-27 9:28 ` Andrew Morton
2004-07-27 12:22 ` Hannes Reinecke
2004-07-27 12:22 ` Hannes Reinecke
2004-07-28 7:12 ` Paul Jackson
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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.