Message-ID: <4DF037C6.4000507@linux.intel.com>
Date: Wed, 08 Jun 2011 20:02:30 -0700
From: Darren Hart <dvhart@linux.intel.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: George Spelvin <linux@horizon.com>
CC: david@rgmadvisors.com, kyle@moffetthome.net, luto@mit.edu,
        linux-kernel@vger.kernel.org
Subject: Re: Change in functionality of futex() system call.
References: <20110609004435.14550.qmail@science.horizon.com>
In-Reply-To: <20110609004435.14550.qmail@science.horizon.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1001
Lines: 26

On 06/08/2011 05:44 PM, George Spelvin wrote:
> I'm not sure if it's best, but the risk of RO waiters interfering could
> be solved by giving them a lower prioirty for wakeup and always waking
> RW-mapped waiters first.

This strikes me as bending over backwards and jumping through hoops
inside the kernel to avoid having to do proper permissions management in
userspace.


> In most cases, there would only be one type of waiter, so this would
> have no effect, but if there were, a RO-mapped reader couldn't "steal"
> wakeup from someone who had it RW-mapped.
> 
> It might conflict with a fairness goal, but it does solve the problem
> without any extension to the API.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/