linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Dabrunz <od@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] hotplug resource limitation
Date: Fri, 20 Aug 2004 19:01:37 +0200	[thread overview]
Message-ID: <20040820170137.GA14601@suse.de> (raw)
In-Reply-To: <41208835.2080702@suse.de>

On 16-Aug-04, Hannes Reinecke wrote:
> Greg KH wrote:
> >On Tue, Aug 10, 2004 at 10:10:02AM +0200, Hannes Reinecke wrote:
> >
> >>Greg KH wrote:
> >>
> >>>On Mon, Aug 09, 2004 at 03:07:15PM +0200, Hannes Reinecke wrote:
> >I'd be very supprised if you could actually measure the hit of adding 2
> >more lines of bash to those hotplug scripts.  They aren't exactly the
> >fastest thing in the world in the first place, nor do they need to be.

On several architectures (most notably s390, but also IPF and PPC) the
load generated by hotplug during boot can in actual practice become
quite high. The bus scans can generate events of the order of 100 to
1000.

These machines are more I/O-focused and handle many devices in parallel.
So having a quick and lean hotplug becomes very desirable.

Since these machines also tend to be used in HA situations, problem
recovery time and therefore reboot time becomes an essential factor to
decrease periods of unavailability.

> But we want to keep the initial 'hotplug' script as small/fast as 
> possible, as this script is called by _every_ event.
> Any subsequent script (e.g. agents) do not really matter, as they are 
> called much more infrequently (here on my local desktop machine I have a 
> ration of 10:1).

-- 
Olaf Dabrunz (od/odabrunz), SUSE Linux AG, Nürnberg


      reply	other threads:[~2004-08-20 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 13:07 [PATCH 2/2] hotplug resource limitation Hannes Reinecke
2004-08-10  0:10 ` Greg KH
2004-08-10  8:10   ` Hannes Reinecke
2004-08-10 21:16     ` Greg KH
2004-08-16 10:11       ` Hannes Reinecke
2004-08-20 17:01         ` Olaf Dabrunz [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=20040820170137.GA14601@suse.de \
    --to=od@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).