From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Rich Felker <dalias@libc.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Davidlohr Bueso <dave@stgolabs.net>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Darren Hart <dvhart@linux.intel.com>,
Mel Gorman <mgorman@suse.de>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Greg Ungerer <gerg@uclinux.org>, Steven Miao <realmz6@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] futex: fix shared futex operations on nommu
Date: Tue, 26 Apr 2016 18:11:07 +0200 [thread overview]
Message-ID: <20160426161107.GF8295@linutronix.de> (raw)
In-Reply-To: <20160426155344.GK21636@brightrain.aerifal.cx>
* Rich Felker | 2016-04-26 11:53:44 [-0400]:
>The whole shared futex logic is meaningless for nommu. Perhaps I
>should have written a better message, though.
>
>With MMU, shared futex keys need to identify the physical backing for
>a memory address because it may be mapped at different addresses in
>different processes (or even multiple times in the same process).
>Without MMU this cannot happen. You only have physical addresses. So
>the "private futex" behavior of using the virtual address as the key
>is always correct (for both shared and private cases) on nommu
>systems.
So using a shared futex on NOMMU does work but it would be more
efficient to always use a private futex instead.
Is this what you are saying?
>Rich
Sebastian
next prev parent reply other threads:[~2016-04-26 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 1:03 [PATCH] futex: fix shared futex operations on nommu Rich Felker
2016-04-26 9:55 ` Sebastian Andrzej Siewior
2016-04-26 15:53 ` Rich Felker
2016-04-26 16:11 ` Sebastian Andrzej Siewior [this message]
2016-04-26 16:27 ` Rich Felker
2016-04-26 22:27 ` Andrew Morton
2016-04-26 22:31 ` Rich Felker
2016-04-27 13:43 ` Thomas Gleixner
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=20160426161107.GF8295@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=dave@stgolabs.net \
--cc=dvhart@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=realmz6@gmail.com \
--cc=tglx@linutronix.de \
--cc=ysato@users.sourceforge.jp \
/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.