From: Roland Dreier <rdreier@cisco.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: fio@vger.kernel.org
Subject: Re: "Fix wrong clock source in mutex" broke fio for me
Date: Wed, 07 Oct 2009 13:22:43 -0700 [thread overview]
Message-ID: <adak4z7osx8.fsf@cisco.com> (raw)
In-Reply-To: <20091007200128.GK8703@kernel.dk> (Jens Axboe's message of "Wed, 7 Oct 2009 22:01:28 +0200")
> I did a quick check, and at least newer revisions have it. Hmm I'm a bit
> torn on this, perhaps the safer option is just to revert the bad commit.
But presumably you made that commit because it fixed some platform?
The default clock for pthread_cond_timedwait() seems poorly specified,
I'm not able to find any definitive statement about what it uses, and
pthread_condattr_setclock() seems to be option in the pthreads spec.
Seems to be a mess.
Anyway not sure what the best idea is....
- R.
next prev parent reply other threads:[~2009-10-07 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 6:56 "Fix wrong clock source in mutex" broke fio for me Roland Dreier
2009-10-07 20:01 ` Jens Axboe
2009-10-07 20:22 ` Roland Dreier [this message]
2009-10-08 6:54 ` Jens Axboe
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=adak4z7osx8.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=fio@vger.kernel.org \
--cc=jens.axboe@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox