From: Pavel Machek <pavel@suse.cz>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"arjan@infradead.org" <arjan@infradead.org>
Subject: Re: [RFC] Imprecise timers.
Date: Tue, 12 Aug 2008 23:58:35 +0200 [thread overview]
Message-ID: <20080812215834.GB12911@elf.ucw.cz> (raw)
In-Reply-To: <20080812181126.GA30061@linux-os.sc.intel.com>
Hi!
> Instead a rounded timer after 5 seconds still ensures atleast 1s idle time on
> the CPU without the overhead.
>
> There can be many users who really don't care about the deadline or can happliy
> use rounded timers or deferrable timers. Say garbage collectors, cache_reap
> and friends, ondemand governor, vga cursor blinking comes to my mind.
Ok, maybe.
But don't try to play with vga cursor blinking; any irregularity there
will be _very_ visible_.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-08-12 21:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 3:02 [RFC] Imprecise timers David Woodhouse
2008-07-22 3:05 ` [RFC] schedule_timeout_range() David Woodhouse
2008-07-22 3:56 ` Nick Piggin
2008-07-22 4:12 ` David Woodhouse
2008-07-22 4:26 ` Arjan van de Ven
2008-07-22 4:34 ` David Woodhouse
2008-07-22 4:33 ` Nick Piggin
2008-07-22 4:45 ` David Woodhouse
2008-07-22 4:50 ` Nick Piggin
2008-07-22 4:58 ` David Woodhouse
2008-07-22 5:35 ` Jan Engelhardt
2008-07-22 4:33 ` Arjan van de Ven
2008-07-22 7:19 ` [RFC] Imprecise timers Rene Herman
2008-07-22 12:54 ` Arjan van de Ven
2008-07-22 14:04 ` Rene Herman
2008-07-29 0:36 ` Pallipadi, Venkatesh
2008-08-09 12:54 ` Pavel Machek
2008-08-11 17:35 ` Venki Pallipadi
2008-08-12 12:00 ` Pavel Machek
2008-08-12 18:11 ` Venki Pallipadi
2008-08-12 21:55 ` Alan Cox
2008-08-12 21:58 ` Pavel Machek [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=20080812215834.GB12911@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=arjan@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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 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).