From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: reading config files with klibc slow
Date: Fri, 12 Mar 2004 16:41:56 +0000 [thread overview]
Message-ID: <20040312164156.GA3738@suse.de> (raw)
fgets from klibc does a read for each single char, which makes it a bit
slow.
Should I fix klibc or change udev to read the config files in bigger chunks?
smirnow:~ # ACTION≠d DEVPATH=/block/loop6 strace -ttfo foo /sbin/udev.static block
smirnow:~ # ACTION≠d DEVPATH=/block/loop6 strace -ttfo bar /sbin/udev block
smirnow:~ # sed '1p;$p;d' foo
19136 17:32:36.351024 execve("/sbin/udev.static", ["/sbin/udev.static", "block"], [/* 50 vars */]) = 0
19136 17:32:40.771209 _exit(0) = ?
smirnow:~ # sed '1p;$p;d' bar
19138 17:32:45.674232 execve("/sbin/udev", ["/sbin/udev", "block"], [/* 50 vars */]) = 0
19138 17:32:45.877024 exit_group(0) = ?
0.2 vs. 4.4 seconds.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
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Ãk
_______________________________________________
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
next reply other threads:[~2004-03-12 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 16:41 Olaf Hering [this message]
2004-03-12 17:06 ` reading config files with klibc slow Kay Sievers
2004-03-12 17:19 ` Olaf Hering
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=20040312164156.GA3738@suse.de \
--to=olh@suse.de \
--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).