From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] cleanup udevstart
Date: Tue, 16 Mar 2004 21:57:55 +0000 [thread overview]
Message-ID: <1079474275.2394.14.camel@pim> (raw)
In-Reply-To: <20040302215536.GA12039@vrfy.org>
On Tue, 2004-03-16 at 18:01, Patrick Mansfield wrote:
> On Tue, Mar 16, 2004 at 03:49:51AM +0100, Kay Sievers wrote:
> >
> > Here are all fgets() converted to mmap(), also the config file read.
> > I get for a very small(20 lines) rules file:
> >
> > time ./udevstart
>
> My timings using lots of scsi_debug LUN's and 1000 line udev.rules got a
> about twice the speedup for klibc compared to your timings (almost 6 times
> faster). None of my udev.rules match, so all 1000 rules are compared even
> for 512 LUNs.
Hey, looks like a pretty nice speedup.
> The inlines of longer functions gains nothing (and probably the other
> inlines in udev.h that are more than 2 lines long and use more than once).
> Not inlining file_map and buf_get_line gives almost no difference in
> times, but shrinks executables a bit.
Yes, I know. It was just a quick hack. I tried to avoid putting "normal"
functions into a header file. If we want this to go in, we may create a
udev_lib.[hc] or something and put in all the generic stuff currently in
udev.h.
> insmod was really this:
>
> modprobe scsi_debug num_tgts2 max_luns\x16 delay=0
>
> Total elapsed times as follows:
>
> insmod rmmod
> klibc current 4:11.42 4:06.27
> klibc patch 0:38.48 0:30.89
> klibc noinline 0:38.33 0:30.89
> glibc current 0:40.84 0:36.20
> glibc with patch 0:40.72 0:32.41
Much thanks for your measurements. It's always better to have real
numbers :)
It seeems that we need to fix it. The mmap() difference for glibc is
pretty small, so it should also be possible to fix the fgets() in klibc.
Any suggestion to go with mmap() or fix klibc instead?
thanks again,
Kay
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-16 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 21:55 [PATCH] cleanup udevstart Kay Sievers
2004-03-02 22:16 ` Greg KH
2004-03-02 23:09 ` Olaf Hering
2004-03-02 23:20 ` Greg KH
2004-03-02 23:23 ` Olaf Hering
2004-03-02 23:32 ` Greg KH
2004-03-15 21:22 ` Olaf Hering
2004-03-16 1:28 ` Kay Sievers
2004-03-16 2:49 ` Kay Sievers
2004-03-16 17:01 ` Patrick Mansfield
2004-03-16 21:57 ` Kay Sievers [this message]
2004-03-16 22:24 ` Patrick Mansfield
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=1079474275.2394.14.camel@pim \
--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 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).