From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] sleep(2) historical question
Date: Wed, 28 Nov 2012 14:57:17 -0500 [thread overview]
Message-ID: <27f4a83f21239ebe7e1a630be9650fe9@coraid.com> (raw)
In-Reply-To: <20121128195432.E430BB827@mail.bitblocks.com>
On Wed Nov 28 14:56:34 EST 2012, bakul@bitblocks.com wrote:
> On Wed, 28 Nov 2012 14:29:19 EST erik quanstrom <quanstro@quanstro.net> wrote:
> >
> > the only problem i see with just adding nsleep is it introduces a
> > second time base, and potentially any time-based call (tsemacquire)
> > would need to be doubled. i would prefer for the end state to be
> > 1 user space time base. but the difficulty is getting there. at the
> > least, the syscall# would change.
>
> If you want to maintain binary compatibility, new syscalls
> would be needed. If you don't care, you can use wrapper
> functions for lower precision calls. Evolution is messy.
just the #, not the name.
- erik
prev parent reply other threads:[~2012-11-28 19:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 23:19 erik quanstrom
2012-11-28 7:37 ` Charles Forsyth
2012-11-28 12:57 ` erik quanstrom
2012-11-28 13:10 ` Charles Forsyth
2012-11-28 13:30 ` erik quanstrom
2012-11-28 14:35 ` Charles Forsyth
2012-11-28 14:46 ` erik quanstrom
2012-11-28 18:58 ` Bakul Shah
2012-11-28 19:10 ` Charles Forsyth
2012-11-28 19:28 ` erik quanstrom
2012-11-28 18:56 ` cinap_lenrek
2012-11-28 19:38 ` Bakul Shah
2012-11-28 20:58 ` Charles Forsyth
2012-11-28 21:02 ` erik quanstrom
2012-11-28 21:13 ` Charles Forsyth
2012-11-28 21:19 ` erik quanstrom
2012-11-28 21:21 ` erik quanstrom
2012-11-28 21:43 ` Bakul Shah
2012-11-29 0:12 ` Charles Forsyth
2012-11-29 8:12 ` arnold
2012-11-29 9:19 ` Charles Forsyth
2012-11-29 15:17 ` erik quanstrom
2012-11-28 19:27 ` David Arnold
2012-11-28 21:12 ` Charles Forsyth
2012-11-28 19:29 ` erik quanstrom
2012-11-28 19:54 ` Bakul Shah
2012-11-28 19:57 ` erik quanstrom [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=27f4a83f21239ebe7e1a630be9650fe9@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).