From: Nicholas Miell <nmiell@comcast.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch 6/9] signalfd/timerfd v3 - timerfd core ...
Date: Sun, 11 Mar 2007 16:52:57 -0700 [thread overview]
Message-ID: <1173657177.2964.9.camel@entropy> (raw)
In-Reply-To: <1173657008.2964.6.camel@entropy>
On Sun, 2007-03-11 at 16:50 -0700, Nicholas Miell wrote:
> You should probably make it behave like the other things that use
> itimerspec, just to avoid confusion -- i.e. timers are relative by
> default, there's a flag that makes them absolute, they expire when
> it_value specifies, and repeat every it_interval nanoseconds if
> it_interval is non-zero.
>
> i.e.
>
> int timerfd(int ufd, int clockid, int flags, const struct timespec
> *utmr);
>
> with TFD_TIMER_ABS in flags making the timer absolute instead of
> relative (and no TFD_TIMER_REL or TFD_TIMER_SEQ at all).
>
Sorry, that should be
int timerfd(int ufd, int clockid, int flags, const struct itimerspec
*utmr);
and TFD_TIMER_ABSTIME.
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2007-03-11 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 23:04 Davide Libenzi
2007-03-11 23:13 ` Davide Libenzi
2007-03-11 23:50 ` Nicholas Miell
2007-03-11 23:52 ` Nicholas Miell [this message]
2007-03-12 0:16 ` Davide Libenzi
2007-03-12 10:19 ` Thomas Gleixner
2007-03-12 18:46 ` Davide Libenzi
2007-03-12 19:00 ` Davide Libenzi
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=1173657177.2964.9.camel@entropy \
--to=nmiell@comcast.net \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®