Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752997AbdHOW5e (ORCPT ); Tue, 15 Aug 2017 18:57:34 -0400 Received: from mail-vk0-f53.google.com ([209.85.213.53]:35009 "EHLO mail-vk0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752930AbdHOW5d (ORCPT ); Tue, 15 Aug 2017 18:57:33 -0400 MIME-Version: 1.0 In-Reply-To: References: <84c7f26182b7f4723c0fe3b34ba912a9de92b8b7.1502758114.git.tim.c.chen@linux.intel.com> <20170815022743.GB28715@tassilo.jf.intel.com> <20170815031524.GC28715@tassilo.jf.intel.com> <20170815224728.GA1373@linux-80c1.suse> From: Linus Torvalds Date: Tue, 15 Aug 2017 15:57:32 -0700 X-Google-Sender-Auth: W0vXSLfbKhFaC3QG9GO_5_STAQk Message-ID: Subject: Re: [PATCH 1/2] sched/wait: Break up long wake list walk To: Linus Torvalds , Andi Kleen , Tim Chen , Peter Zijlstra , Ingo Molnar , Kan Liang , Andrew Morton , Johannes Weiner , Jan Kara , linux-mm , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 570 Lines: 16 On Tue, Aug 15, 2017 at 3:56 PM, Linus Torvalds wrote: > > Except they really don't actually work for this case, exactly because > they also simplify away "minor" details like exclusive vs > non-exclusive etc. > > The page wait-queue very much has a mix of "wake all" and "wake one" semantics. Oh, and the page wait-queue really needs that key argument too, which is another thing that swait queue code got rid of in the name of simplicity. So no. The swait code is absolutely _entirely_ the wrong thing to use. Linus