All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [GIT] Experimental threaded udev
Date: Mon, 01 Jun 2009 13:30:04 +0000	[thread overview]
Message-ID: <1243863004.28812.8.camel@yio.site> (raw)
In-Reply-To: <4A1EA138.10400@tuffmail.co.uk>

On Mon, 2009-06-01 at 14:33 +0200, Kay Sievers wrote:

> Here is version 2 of the patch, with a few things corrected.

Pretty weird test, but it seems to survive on my Dual Core 1.5 GHz
laptop:

Create lots of devices:
  $ time (modprobe scsi_debug add_host\x16 max_luns2 num_tgts\x16 num_parts=2; udevadm settle)
  real	11m28.193s

23.000 block devices:
  $ find /sys/class/block/ | wc -l
  23824

72.000 sysfs devices:
  $ find /sys/ -name uevent | wc -l
  72224

We created 262 workers:
  $ ps afx | grep udevd | wc -l
  262

And 10 seconds later, all workers are gone:
  $ ps afx | grep udevd | wc -l
  2

Kay


  parent reply	other threads:[~2009-06-01 13:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 14:35 [GIT] Experimental threaded udev Alan Jenkins
2009-05-28 15:09 ` Kay Sievers
2009-05-28 15:39 ` Alan Jenkins
2009-05-29 17:53 ` Alan Jenkins
2009-05-29 18:11 ` Kay Sievers
2009-06-01  2:41 ` Kay Sievers
2009-06-01  9:29 ` Alan Jenkins
2009-06-01 11:32 ` Kay Sievers
2009-06-01 12:33 ` Kay Sievers
2009-06-01 13:30 ` Kay Sievers [this message]
2009-06-01 13:46 ` Alan Jenkins
2009-06-01 13:57 ` Kay Sievers
2009-06-01 16:22 ` Kay Sievers
2009-06-01 16:24 ` Alan Jenkins
2009-06-01 19:39 ` Kay Sievers
2009-06-02  4:58 ` Kay Sievers
2009-06-02  9:13 ` Alan Jenkins
2009-06-02  9:26 ` Alan Jenkins
2009-06-02 11:39 ` Kay Sievers
2009-06-02 14:05 ` Kay Sievers
2009-06-03 19:44 ` Kay Sievers
2009-06-03 20:46 ` Alan Jenkins
2009-06-03 22:20 ` Kay Sievers
2009-06-03 23:53 ` Kay Sievers
2009-06-06 14:20 ` Kay Sievers
2009-06-06 17:01 ` Bryan Kadzban
2009-06-08 11:45 ` Scott James Remnant
2009-06-08 16:29 ` Bryan Kadzban

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=1243863004.28812.8.camel@yio.site \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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.