From: Randy Dunlap <rdunlap@infradead.org>
To: Ryan Nicholl <r.p.nicholl@gmail.com>, linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Futex Question (64 bits?)
Date: Mon, 21 Apr 2014 10:50:23 -0700 [thread overview]
Message-ID: <53555A5F.4040500@infradead.org> (raw)
In-Reply-To: <CAPuLQKxoc3Gk3_xKetSOzFLg5s36P3MJ7Jy=15_JmwYp2J_v+g@mail.gmail.com>
[adding Rusty]
On 03/24/2014 02:19 PM, Ryan Nicholl wrote:
> I would like to know if it would be possible to use a 64 bit futex
> call? If not, I would like to request it be added. (It is acknowledged
> in the manpages that it must be added eventually anyway.)
>
> I am programming a C++11+ library. One of the constructed features is
> a "locking pointer". Unfortunately, pointers are usually 64 bits,
> while the futex call supports only 32 bits. I could not discover any
> documented way to invoke a 64 bit futex call.
>
> It's unfortunate in that the futex call must have a timeout set
> because of the possible deadlock condition where only the half of the
> pointer not futexed is modified between the time the system call is
> entered and executed.
>
> This creates a situation that prevents the locking_ptr from being
> realtime safe unless the timeout is set at a very low value.
> Furthermore, this causes excess CPU usage due to spurious wakeups.
>
> Thank you,
> Ryan Nicholl
> --
--
~Randy
next prev parent reply other threads:[~2014-04-21 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 21:19 Futex Question (64 bits?) Ryan Nicholl
2014-04-21 17:50 ` Randy Dunlap [this message]
2014-04-23 5:28 ` Rusty Russell
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=53555A5F.4040500@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.p.nicholl@gmail.com \
--cc=rusty@rustcorp.com.au \
/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