Received: by 2002:a17:90a:bc8d:0:0:0:0 with SMTP id x13csp1159565pjr; Thu, 21 May 2020 01:18:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwrh+m5twxPbJslF7ydpcFdfCD4qp+T2/uueUBLf2pVAbDwfhUw25EDURyKUp69OPU0ByJj X-Received: by 2002:a50:a883:: with SMTP id k3mr4180500edc.198.1590049086005; Thu, 21 May 2020 01:18:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590049085; cv=none; d=google.com; s=arc-20160816; b=dPgO4WSHRnC+j0aCXzNNx9omrKwnrO+pViAzxt6ec6SRDq/W+c2LHMz/7RExdFwlDx c4dPeOJ5uSp89MymMA9lpK6hMR9ey35p/canom0Fu4KA9RfTs1tPa6z1QOkz+HjcgxR0 //SdAB8vUVNPL4I2ffhvKjfW89UcTo1aHK2Vl8jmhQda/96VZCPaVT6BKWbQL0QtE4+j p4hi3x4/JMSg6TR41HNivKiHqOi/aNBlqvVl+Hs0/U4iRpgCpMK44W6K5MgY7nUDOC4r qhs64hZlc9K9Iv7r4Fk3I5n9GbMdrOrdt+XZXgg8ejD72PmlJKxYI8jjD41jpJ74E2xs B0Bw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=hCPRagowRGsHn6RLR0wzqIDoPYLXJrusoeDww3UvwZc=; b=Ab6B+qPdJdfF9m7CkHojF8F7xbGHLD2a4V6uSI95aiIc1cDyJztlVRxiZysn4LNudJ fT72TFtwt36CbV7XyDJJ1eW/Irf7FS1khpqhSeGQ0HCUvJCx5MwghWnw/bLJvHwcPjGA TTncWTb+BoiZTnYVCSnSWVmgX8IBrNT7dwnPzvmfQ+a7Pd8x0I4dIoBmtOTEcrtpxMyj hryqIb6ht2MkLHec6vv1Z4TrUbKjnvg7tUPsTDC76ycsXof971mwavpcOclDB0Cj+noh e20ew0qI5I2E+148v6y2m/mTT3+z1Knp6tOe1g9p522PzZd5vf26xGt6H6petLhknEtG e5oQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h63si2484514edd.451.2020.05.21.01.17.42; Thu, 21 May 2020 01:18:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728494AbgEUIOV (ORCPT + 99 others); Thu, 21 May 2020 04:14:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52970 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727122AbgEUIOV (ORCPT ); Thu, 21 May 2020 04:14:21 -0400 Received: from Galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 65600C061A0E; Thu, 21 May 2020 01:14:21 -0700 (PDT) Received: from p5de0bf0b.dip0.t-ipconnect.de ([93.224.191.11] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jbgL2-0004jF-Gl; Thu, 21 May 2020 10:14:00 +0200 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id B6DB5100C2D; Thu, 21 May 2020 10:13:59 +0200 (CEST) From: Thomas Gleixner To: Ming Lei Cc: Jens Axboe , Christoph Hellwig , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, John Garry , Bart Van Assche , Hannes Reinecke , io-uring@vger.kernel.org, Peter Zijlstra Subject: Re: io_uring vs CPU hotplug, was Re: [PATCH 5/9] blk-mq: don't set data->ctx and data->hctx in blk_mq_alloc_request_hctx In-Reply-To: <20200521022746.GA730422@T590> References: <20200519015420.GA70957@T590> <20200519153000.GB22286@lst.de> <20200520011823.GA415158@T590> <20200520030424.GI416136@T590> <20200520080357.GA4197@lst.de> <8f893bb8-66a9-d311-ebd8-d5ccd8302a0d@kernel.dk> <448d3660-0d83-889b-001f-a09ea53fa117@kernel.dk> <87tv0av1gu.fsf@nanos.tec.linutronix.de> <2a12a7aa-c339-1e51-de0d-9bc6ced14c64@kernel.dk> <87eereuudh.fsf@nanos.tec.linutronix.de> <20200521022746.GA730422@T590> Date: Thu, 21 May 2020 10:13:59 +0200 Message-ID: <87367tvh6g.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ming Lei writes: > On Thu, May 21, 2020 at 12:14:18AM +0200, Thomas Gleixner wrote: >> When the CPU is finally offlined, i.e. the CPU cleared the online bit in >> the online mask is definitely too late simply because it still runs on >> that outgoing CPU _after_ the hardware queue is shut down and drained. > > IMO, the patch in Christoph's blk-mq-hotplug.2 still works for percpu > kthread. > > It is just not optimal in the retrying, but it should be fine. When the > percpu kthread is scheduled on the CPU to be offlined: > > - if the kthread doesn't observe the INACTIVE flag, the allocated request > will be drained. > > - otherwise, the kthread just retries and retries to allocate & release, > and sooner or later, its time slice is consumed, and migrated out, and the > cpu hotplug handler will get chance to run and move on, then the cpu is > shutdown. 1) This is based on the assumption that the kthread is in the SCHED_OTHER scheduling class. Is that really a valid assumption? 2) What happens in the following scenario: unplug mq_offline set_ctx_inactive() drain_io() io_kthread() try_queue() wait_on_ctx() Can this happen and if so what will wake up that thread? I'm not familiar enough with that code to answer #2, but this really wants to be properly described and documented. Thanks, tglx