public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.name>
To: Greg KH <greg@kroah.com>, Nick Craig-Wood <ncw1@axis.demon.co.uk>
Cc: Sean Neakums <sneakums@zork.net>, linux-kernel@vger.kernel.org
Subject: Re: hotplug (was devfs)
Date: Thu, 14 Nov 2002 12:46:12 +0100	[thread overview]
Message-ID: <200211141246.12833.oliver@neukum.name> (raw)
In-Reply-To: <20021113170204.GC5446@kroah.com>


> > So - perhaps hotplug ought to be serialised?
>
> No, it's not needed for this problem.  There has been talk of
> serializing stuff in userspace, which is the proper way to handle some
> of the remove before add was seen problems.

We may need some kind of load control.
The thought of firing up hundreds of hotplug scripts
simultaneously is not pretty.

	Regards
		Oliver


  parent reply	other threads:[~2002-11-14 11:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  9:32 devfs Ian Molton
2002-11-12  9:43 ` devfs Xavier Bestel
2002-11-12  9:49   ` devfs john slee
2002-11-12 10:01     ` devfs Sean Neakums
2002-11-12 12:51       ` devfs Oliver Neukum
2002-11-13 10:48         ` hotplug (was devfs) Nick Craig-Wood
2002-11-13 17:02           ` Greg KH
2002-11-13 18:06             ` Nick Craig-Wood
2002-11-13 18:04               ` Greg KH
2002-11-14 11:46             ` Oliver Neukum [this message]
2002-11-12 10:05     ` devfs Xavier Bestel
2002-11-12 10:04   ` devfs Alexander Viro
2002-11-12 10:25     ` devfs Ian Molton
2002-11-12 10:46       ` devfs Dave Jones
2002-11-12 11:08         ` devfs Ian Molton
2002-11-12 11:24         ` devfs Rando Christensen
2002-11-12 13:30           ` devfs Alexander Viro
2002-11-12 14:53         ` devfs Alan Cox
2002-11-12 15:37           ` devfs Ian Molton
2002-11-12 11:29     ` devfs Helge Hafting
2002-11-12 15:40   ` devfs Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2002-11-13 18:45 hotplug (was devfs) Ed Vance
2002-11-13 18:45 ` Greg KH
2002-11-13 18:59 Ed Vance

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=200211141246.12833.oliver@neukum.name \
    --to=oliver@neukum.name \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncw1@axis.demon.co.uk \
    --cc=sneakums@zork.net \
    /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