From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 022 release
Date: Sat, 13 Mar 2004 08:29:58 +0000 [thread overview]
Message-ID: <20040313082957.GA13388@kroah.com> (raw)
In-Reply-To: <20040313000729.GA10821@kroah.com>
On Sat, Mar 13, 2004 at 03:00:28AM +0100, Kay Sievers wrote:
> On Sat, 2004-03-13 at 01:07, Greg KH wrote:
> > Oh, I'd like to thank OSDL for doing some preliminary speed tests (as
> > well as functionality tests) on udev. Unofficially it looks like it
> > only took 7 seconds extra to use udev to name 1000 scsi disks (and the
> > rule was calling out to scsi_id for every disk, and then parsing over
> > 1000 rules.) Note that is 7 seconds extra to name _all_ of the disks at
> > once using the scsi_debug module. That's not too shabby at all.
>
> Sounds really nice.
> Do you know if they are using udevd or calling udev directly?
I'm pretty sure they are using udevsend, udev, and udev like it is
installed by default as. But I can't be sure.
The report is at:
http://developer.osdl.org/maryedie/DCL/PSDN/Testing_udev_notes.html
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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
prev parent reply other threads:[~2004-03-13 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 0:07 [ANNOUNCE] udev 022 release Greg KH
2004-03-13 2:00 ` Kay Sievers
2004-03-13 8:29 ` Greg KH [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=20040313082957.GA13388@kroah.com \
--to=greg@kroah.com \
--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 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).