From: Chris Friesen <cfriesen@nortel.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
albert@users.sourceforge.net, paulus@samba.org,
schwidefsky@de.ibm.com, mahuja@us.ibm.com, donf@us.ibm.com,
mpm@selenic.com, benh@kernel.crashing.org
Subject: Re: [RFC][PATCH] new timeofday-based soft-timer subsystem
Date: Tue, 03 May 2005 11:22:20 -0600 [thread overview]
Message-ID: <4277B34C.4000403@nortel.com> (raw)
In-Reply-To: <20050503170224.GA2776@us.ibm.com>
Nishanth Aravamudan wrote:
> but then there is another issue: the restart_block used by
> sys_nanosleep() only allows for 4 unsigned long arguments, when, in
> fact, nanoseconds are a 64-bit quantity in the kernel. As long as the
> nanosleep() request is no more than around 4 seconds, we should be ok
> using unsigned longs.
My man page for nanosleep specifies that the "nanoseconds" portion of
the timespec must be under 1 billion and is of type "long". Is that no
longer valid?
Chris
next prev parent reply other threads:[~2005-05-03 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 22:45 [RFC][PATCH (1/4)] new timeofday core subsystem (v A4) john stultz
2005-04-29 22:46 ` [RFC][PATCH (2/4)] new timeofday arch specific hooks " john stultz
2005-04-29 22:47 ` [RFC][PATCH (3/4)] new timeofday arch specific timesource drivers " john stultz
2005-04-29 22:48 ` [RFC][PATCH (4/4)] new timeofday vsyscall proof of concept " john stultz
2005-05-02 21:13 ` [RFC][PATCH (2/4)] new timeofday arch specific hooks " Pavel Machek
2005-05-02 21:28 ` john stultz
2005-04-29 23:35 ` [RFC][PATCH] new timeofday-based soft-timer subsystem Nishanth Aravamudan
2005-05-02 18:41 ` Darren Hart
2005-05-03 17:02 ` Nishanth Aravamudan
2005-05-03 17:22 ` Chris Friesen [this message]
2005-05-03 18:07 ` Nish Aravamudan
2005-05-03 21:47 ` Nishanth Aravamudan
2005-04-29 23:44 ` [RFC][PATCH (1/4)] new timeofday core subsystem (v A4) john stultz
2005-04-29 23:50 ` Benjamin Herrenschmidt
2005-04-30 0:33 ` john stultz
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=4277B34C.4000403@nortel.com \
--to=cfriesen@nortel.com \
--cc=albert@users.sourceforge.net \
--cc=benh@kernel.crashing.org \
--cc=donf@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mahuja@us.ibm.com \
--cc=mpm@selenic.com \
--cc=nacc@us.ibm.com \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.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 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.