Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754750Ab0D1Oxs (ORCPT ); Wed, 28 Apr 2010 10:53:48 -0400 Received: from mail-pw0-f46.google.com ([209.85.160.46]:62333 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751581Ab0D1Oxq convert rfc822-to-8bit (ORCPT ); Wed, 28 Apr 2010 10:53:46 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=lFWwhHToMSZQ1TjC8wvd5otMovFWFTg1XW0QiP2b1BFPdfGOi3XCeh+rWbE46Up0/z d3FU9KsYmc9M03OixQZVAucDfz0jaPeuEM7M8B917fgC0m2Q7EC2F766aJJYTMOEe3+K 8rjNHuHEyA9H1gpVO1CItHiKG4qYgPyzBCEH0= MIME-Version: 1.0 In-Reply-To: <6096.1272463619@redhat.com> References: <1272430986-20436-1-git-send-email-xiaosuo@gmail.com> <8526.1272447122@redhat.com> <6096.1272463619@redhat.com> From: Changli Gao Date: Wed, 28 Apr 2010 22:53:16 +0800 Message-ID: Subject: Re: [RFC] sched: implement the exclusive wait queue as a LIFO queue To: David Howells Cc: Ingo Molnar , Alexander Viro , Andrew Morton , "Eric W. Biederman" , Davide Libenzi , Roland Dreier , Stefan Richter , Peter Zijlstra , "David S. Miller" , Eric Dumazet , Christoph Lameter , Andreas Herrmann , Thomas Gleixner , Takashi Iwai , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 916 Lines: 23 On Wed, Apr 28, 2010 at 10:06 PM, David Howells wrote: > > I suspect you really want to have the semantics defined per-queue.  _Either_ a > queue is FIFO (such as processes waiting for a resource so they can do > something with it) _or_ it is LIFO (such as a pool of processes waiting to be > given work). > > How often do the two actually mix?  And if they do, is that really an error? > The sock.sk_sleep is used by exclusive and non-exclusive wait queues. exclusive and non-exclusive is identified by wait queues, not wait queue heads. Maybe there is a historical reason. It is much like a hack. -- Regards, Changli Gao(xiaosuo@gmail.com) -- 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/