From: george anzinger <george@mvista.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
high-res-timers-discourse@lists.sourceforge.net
Subject: Re: [PATCH] High-res-timers part 1 (core)
Date: Thu, 26 Sep 2002 18:06:36 -0700 [thread overview]
Message-ID: <3D93AF1C.13F96D79@mvista.com> (raw)
In-Reply-To: 20020926205808.A15402@redhat.com
Benjamin LaHaise wrote:
>
> On Thu, Sep 26, 2002 at 05:16:35PM -0700, george anzinger wrote:
> > hash list. This change makes it easy to configure the list
> > size for those who are concerned with performance. It also
> > eliminates the "time out" for the cascade operation every
>
> Could you make the list size configurable at boot time or by sysctl?
> It's almost impossible for distro vendors to get these kinds of tunables
> right for everyone, so making them dynamic is preferred.
>
> -ben
Hm, that would require dynamic allocation of the memory,
probably not an issue, but the masks would also need to be
dynamic. The question is is it worth it. The 512 entry
list seems to handle a very large number of timers with no
trouble. We did tests measuring timer arm times with 4000
timers in the list. The slope was so low that we did not
even try to increase the list size.
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-09-27 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 0:16 [PATCH] High-res-timers part 1 (core) george anzinger
2002-09-27 0:58 ` Benjamin LaHaise
2002-09-27 1:06 ` george anzinger [this message]
2002-09-27 2:21 ` Andrew Morton
2002-09-27 3:07 ` george anzinger
2002-09-27 14:52 ` Dave McCracken
2002-09-27 15:26 ` george anzinger
2002-09-27 17:40 ` Chris Wedgwood
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=3D93AF1C.13F96D79@mvista.com \
--to=george@mvista.com \
--cc=bcrl@redhat.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).