From: Arjan van de Ven <arjan@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@tglx.de,
torvalds@linux-foundation.org
Subject: Re: update on hrtimer based select/poll and range-hrtimers
Date: Sun, 7 Sep 2008 14:07:46 -0700 [thread overview]
Message-ID: <20080907140746.3de99747@infradead.org> (raw)
In-Reply-To: <1220820399.8687.103.camel@twins.programming.kicks-ass.net>
On Sun, 07 Sep 2008 22:46:39 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> > "0.1% of the time" for not-nice, not realtime tasks
> > "0.5% of the time" for nice, not realtime tasks
> > with a cap of 100msec for both.
> >
> > I would like to request feedback on this approach; I think this is
> > better than the "hardcoded steps" as before, but maybe someone can
> > come up with an ever better idea....
>
> logarithms pop to mind (again :-)
and it still doesn't strike me as "oh yeah"
how would you see this work? Can you give a numeric example?
>
> > static unsigned long __estimate_accuracy(struct timespec *tv)
> > {
> > unsigned long slack;
> > int divfactor = 1000;
> >
> > if (task_nice(current))
>
> This triggers for both -nice and +nice tasks, it might be worth
> differentiating between those.
good spotting; will fix.
> >
> > if (current->policy == SCHED_FIFO ||
> > current->policy == SCHED_RR)
> > return 0;
>
> rt_task(current) ?
hmm that's not exactly equivalent.. I can see either but still.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-09-07 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 18:11 update on hrtimer based select/poll and range-hrtimers Arjan van de Ven
2008-09-07 20:46 ` Peter Zijlstra
2008-09-07 21:07 ` Arjan van de Ven [this message]
2008-09-08 14:31 ` Ingo Molnar
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=20080907140746.3de99747@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@tglx.de \
--cc=torvalds@linux-foundation.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 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.