From: George Anzinger <george@mvista.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
matthias@corelatus.se,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: patch to fix set_itimer() behaviour in boundary cases
Date: Fri, 21 Jan 2005 00:22:45 -0800 [thread overview]
Message-ID: <41F0BBD5.1010006@mvista.com> (raw)
In-Reply-To: <1106293769.4182.64.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>>>This one I meant to fix in the kernel fwiw; we can put that loop inside
>>>the kernel easily I'm sure
>>
>>Yes, but it will increase the data size of the timer...
>>
>
>
> eh how?
> the way I think it can be done is to just have multiple timers fire
> until the total time is up. It's not a performance issue (a timer firing
> every 24 days.. who cares, esp since such long delays are rare anyway)
> after all...
Sure that works, but you still need to keep info around on when the timer is
supposed to expire. This will be at least two words (u64)jiffies_expire_time.
This would likly end up in the task struc along with the timer itself.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
prev parent reply other threads:[~2005-01-21 8:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 8:45 patch to fix set_itimer() behaviour in boundary cases Matthias Lang
2005-01-15 9:30 ` Andrew Morton
2005-01-15 9:36 ` William Lee Irwin III
2005-01-15 9:58 ` Arjan van de Ven
2005-01-15 10:07 ` William Lee Irwin III
2005-01-15 19:55 ` Chris Wedgwood
2005-01-15 20:20 ` Arjan van de Ven
2005-01-15 23:25 ` Matthias Lang
2005-01-15 23:39 ` Randy.Dunlap
2005-01-16 0:58 ` Alan Cox
2005-01-16 12:11 ` Arjan van de Ven
2005-01-19 23:51 ` George Anzinger
2005-01-20 8:07 ` Arjan van de Ven
2005-01-20 23:12 ` George Anzinger
2005-01-21 7:49 ` Arjan van de Ven
2005-01-21 8:22 ` 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=41F0BBD5.1010006@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias@corelatus.se \
/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.