From: Rusty Russell <rusty@rustcorp.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL] kstrdup
Date: Sun, 20 Apr 2003 18:05:40 +1000 [thread overview]
Message-ID: <20030420081206.C68A62C01A@lists.samba.org> (raw)
In-Reply-To: Your message of "19 Apr 2003 13:27:21 +0100." <1050755240.3277.3.camel@dhcp22.swansea.linux.org.uk>
In message <1050755240.3277.3.camel@dhcp22.swansea.linux.org.uk> you write:
> On Sad, 2003-04-19 at 05:48, Jeff Garzik wrote:
> > And? It's still slower.
>
> You are arguing over a 1 instruction, probably sub 1 clock scheduling
> matter on a call which is not used on any fast or common path. If you
> shaved 1 clock off the timer handling instead you'd make a lot more
> difference..
Hey, if we have 50 million machines running 2.6 for three years, this
optimization saves 100 clock cycles per boot (most kstrdups are device
init), and machines boot once a month, and average 1GHz, that's three
minutes of saved time.
I think Jeff and I should start the kstrdup sourceforge project
immediately...
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2003-04-20 8:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 7:58 [TRIVIAL] kstrdup Rusty Trivial Russell
2003-04-18 8:10 ` Jeff Garzik
2003-04-18 16:20 ` Linus Torvalds
2003-04-18 16:56 ` Jeff Garzik
2003-04-18 18:00 ` Linus Torvalds
2003-04-18 18:44 ` Jeff Garzik
2003-04-19 4:52 ` Rusty Russell
2003-04-18 18:00 ` Richard B. Johnson
2003-04-18 18:40 ` Jeff Garzik
2003-04-18 19:24 ` H. Peter Anvin
2003-04-18 23:37 ` Alan Cox
2003-04-18 19:29 ` Richard B. Johnson
2003-04-19 11:45 ` Kai Henningsen
2003-04-19 20:16 ` Ruth Ivimey-Cook
2003-04-19 4:14 ` Rusty Russell
2003-04-19 4:48 ` Jeff Garzik
2003-04-19 8:28 ` Rusty Russell
2003-04-19 12:27 ` Alan Cox
2003-04-19 14:44 ` Bernd Eckenfels
2003-04-20 8:05 ` Rusty Russell [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=20030420081206.C68A62C01A@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.