From: James Chapman <jchapman@katalix.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: netdev@vger.kernel.org, hadi@cyberus.ca, davem@davemloft.net,
jeff@garzik.org, mandeep.baines@gmail.com, ossthema@de.ibm.com
Subject: Re: RFC: possible NAPI improvements to reduce interrupt rates for low traffic rates
Date: Mon, 10 Sep 2007 10:25:57 +0100 [thread overview]
Message-ID: <46E50DA5.8050403@katalix.com> (raw)
In-Reply-To: <p737in19kxw.fsf@bingen.suse.de>
Andi Kleen wrote:
> James Chapman <jchapman@katalix.com> writes:
> On some platforms the precise timers (like ktime_get()) can be slow,
> but often they are fast. It might make sense to use a shorter
> constant time wait on those with fast timers at least. Right now this
> cannot be known by portable code, but there was a proposal some time
> ago to export some global estimate to tell how fast
> ktime_get().et.al. are. That could be reviewed.
Interesting. Is ktime_get() fast enough on P4 systems? I'll be using
those to test with.
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
next prev parent reply other threads:[~2007-09-10 9:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 14:16 RFC: possible NAPI improvements to reduce interrupt rates for low traffic rates James Chapman
2007-09-06 14:37 ` Stephen Hemminger
2007-09-06 15:30 ` James Chapman
2007-09-06 15:37 ` Stephen Hemminger
2007-09-06 16:07 ` James Chapman
2007-09-06 23:06 ` jamal
2007-09-07 9:31 ` James Chapman
2007-09-07 13:22 ` jamal
2007-09-10 9:20 ` James Chapman
2007-09-10 12:27 ` jamal
2007-09-12 7:04 ` Bill Fink
2007-09-12 12:12 ` jamal
2007-09-12 13:50 ` James Chapman
2007-09-12 14:02 ` Stephen Hemminger
2007-09-12 16:26 ` James Chapman
2007-09-12 16:47 ` Mandeep Baines
2007-09-13 6:57 ` David Miller
2007-09-14 13:14 ` jamal
2007-09-07 21:20 ` Jason Lunz
2007-09-10 9:25 ` James Chapman
2007-09-07 3:55 ` Mandeep Singh Baines
2007-09-07 9:38 ` James Chapman
2007-09-08 16:42 ` Mandeep Singh Baines
2007-09-10 9:33 ` James Chapman
2007-09-10 12:12 ` jamal
2007-09-08 16:32 ` Andi Kleen
2007-09-10 9:25 ` James Chapman [this message]
2007-09-12 15:12 ` David Miller
2007-09-12 16:39 ` James Chapman
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=46E50DA5.8050403@katalix.com \
--to=jchapman@katalix.com \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=jeff@garzik.org \
--cc=mandeep.baines@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ossthema@de.ibm.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.