public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH RT] make hrtimer_nanosleep return immediately if time has passed
Date: Tue, 10 Jan 2006 11:46:56 -0800	[thread overview]
Message-ID: <43C40F30.1010009@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601092042260.11138@gandalf.stny.rr.com>

Steven Rostedt wrote:
> On Mon, 9 Jan 2006, George Anzinger wrote:
> 
>>Steven Rostedt wrote:
>>
>>Uh... I have been wondering about the "mode" thing, thinking "flags" might be
>>better.  And allowing, say, a "return if elapsed" flag as well as the ABS
>>flag.  Then all you would need to do is to add the "return if elapsed" flag
>>to the nanosleep calls.  I have other reasons for wanting to expand the
>>"mode" to more that two states... but, even with out that, I think the result
>>would be a) less code, and b) easier to follow and understand.  I just have
>>trouble pushing a word on the stack to make a call and then use only one bit
>>of it when it could be combined...
> 
> 
> And I perfectly agree with you :)
> 
> The problem is that the hrtimes is not my code, and I don't like doing
> too many changes in code that I don't understand the consequences of. As
> you showed me earlier, that the previous change broke the posix_timers.
> So I really only did the bare minimum to fix what I considered a bug, and
> let Thomas, John, Ingo or yourself do a proper fix.  Someone that
> understands the timers better than I do.
> 
> Currently, it seems those people are too busy, and I just wanted a quick
> fix.  I personally didn't like the patch, but my nose is stuck more into
> the scheduling, memory and Ingo's rt_mutex now to spend time understanding
> all the timer code. ;)
> 
I am working on a general clean up of this area.  I will roll you idea into 
it and see what they say.
> 


-- 
George Anzinger   george@mvista.com
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/

      reply	other threads:[~2006-01-10 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 14:18 [PATCH RT] make hrtimer_nanosleep return immediately if time has passed Steven Rostedt
2006-01-06 22:27 ` George Anzinger
2006-01-06 23:03   ` Steven Rostedt
2006-01-10  1:36     ` George Anzinger
2006-01-10  1:49       ` Steven Rostedt
2006-01-10 19:46         ` George Anzinger [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=43C40F30.1010009@mvista.com \
    --to=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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