From: <cutaway@bellsouth.net>
To: "Florin Malita" <fmalita@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6 speed
Date: Tue, 26 Jul 2005 01:55:18 -0400 [thread overview]
Message-ID: <012401c591a6$9a2e2040$0b00000a@solidwaste> (raw)
In-Reply-To: f8994115050724211071a3dbe1@mail.gmail.com
----- Original Message -----
From: "Florin Malita" <fmalita@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Sent: Monday, July 25, 2005 12:10 AM
Subject: Re: kernel 2.6 speed
> On 7/24/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > time() isn't a hot
> > path in the real world.
>
> That's what you would expect but I've straced stuff calling
> gettimeofday() in huge bursts every other second. Obviously braindead
> stuff but so is "the real world" most of the time() ... :)
Anything time stamping things it processes many of will call some sort of
time function pretty often. Could happen frequently with certain classes of
applications. OS/2's "infoseg" approach was a pretty "high speed low
drag" way to eliminate a trip into the kernel for all but the most esoteric
time requirements.
next prev parent reply other threads:[~2005-07-26 5:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 19:12 kernel 2.6 speed Ciprian
2005-07-24 19:41 ` Brice Goglin
2005-07-24 19:47 ` Dag Nygren
2005-07-24 20:40 ` Puneet Vyas
2005-07-24 21:03 ` Florin Malita
2005-07-24 22:49 ` Lee Revell
2005-07-25 19:52 ` Bill Davidsen
2005-07-24 21:46 ` Jan Engelhardt
2005-07-24 23:47 ` Alan Cox
2005-07-25 4:10 ` Florin Malita
2005-07-25 5:18 ` Willy Tarreau
2005-07-25 6:47 ` Ciprian
2005-07-26 5:55 ` cutaway [this message]
2005-07-26 19:45 ` Florin Malita
-- strict thread matches above, loose matches on Subject: below --
2005-08-03 15:31 Henrik Holst
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='012401c591a6$9a2e2040$0b00000a@solidwaste' \
--to=cutaway@bellsouth.net \
--cc=fmalita@gmail.com \
--cc=linux-kernel@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