From: Arnd Bergmann <arnd@arndb.de>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: [RFC PATCH 0/3] RFC: using hrtimers for in-kernel timeouts
Date: Mon, 05 Mar 2007 01:20:24 +0100 [thread overview]
Message-ID: <20070305002024.875968120@arndb.de> (raw)
I've played around with the new timer statistics to see which timers might
benefit of being moved from traditional timers to hrtimers.
Since my understanding is that timer_list timers are not really meant to
expire, this seems to include a lot of what comes in through
schedule_timeout, in particular select() and futex wait.
I have no idea if what I was attempting is even the right approach to
start with, but I want to share the patches in case it is ;-).
Maybe someone is interested in running some low-level benchmarks on this
or point out any bugs in the code.
Arnd <><
--
next reply other threads:[~2007-03-05 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 0:20 Arnd Bergmann [this message]
2007-03-05 0:20 ` [RFC PATCH 1/3] introduce schedule_timeout_hr Arnd Bergmann
2007-03-05 0:20 ` [RFC PATCH 2/3] use hrtimer in select and pselect Arnd Bergmann
2007-03-05 0:20 ` [RFC PATCH 3/3] change schedule_timeout to use hrtimers Arnd Bergmann
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=20070305002024.875968120@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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