Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp649629ybk; Wed, 20 May 2020 08:33:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxO31JgwqJP46IUdeG5mA+Gi+C1bvziqkrNk2G6prhkUbqc4Bj7nk9+sA7A0g9V8Q25zN37 X-Received: by 2002:a05:6402:2213:: with SMTP id cq19mr3969248edb.337.1589988829601; Wed, 20 May 2020 08:33:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589988829; cv=none; d=google.com; s=arc-20160816; b=qB1dVrftGhNqoHonCc18dOhYJr14ZAYzQuiabnH42SRe2wtjIAzG+tgRP/coHXdH1F QgtbiFbUy3N0qhktpyF4Z2flss+hBX1zCVMGNHc7A30QMykSq5NQEKwFpTL7uDSaO2ZS AT6piQhX2xXO3jj6R7zvOJb5lpc9wVgAJE2KTCZcG6z3GjpFJ59zqsMYjHLsuCEkVD0M g8AoAshpVRCiD8WjWzS5QgULBmXYe+XzkcISMRgNBhXqSZvvIOEla+hhyfgoC+vlQc6s hDepJTK+sDZmgkXVvAvjJrfqA/qPL2KQVNb0+zfG3iYFHejqUC+xjCyB31Kkme5Xr/co 4Y6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=c1gH1nekoXyFyeeBY8u62RAQ3kmFS1CUrd7Hw1DiKX8=; b=uKlO8ijzck32Y59zet0yMh4/KXBG9TxnhCgzC82MqBAxIiPIMzwJGFmiXzZpRurGGo SCnJ7B/F8Jstuyu9dQqNuNsKL4j7JXgJko9KUEgda8pWbyLjgomjRTLxMg64+vEMGOy1 dfJ7BstnIRoGof/N2yPG2Hg0f/YxLwn6oqeM93ZY8LCcEVLI9JRgYyecgQudLiko5CNj 9fNHH4Uj/tpmeaOmEofs9ZAz4wUftfVPcGgJ0MbGYEoCB3BnRscN56vnaofuXpK8cJcC h9QLDpBCXMhiWgQw9C9MFiBgaKK7u3bShHEQAgLAJbnGZJtIQiMVZ7aWZOUNNS9OX6qR aBiQ== 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 ce14si60891edb.101.2020.05.20.08.33.21; Wed, 20 May 2020 08:33:49 -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 S1726896AbgETPb3 (ORCPT + 99 others); Wed, 20 May 2020 11:31:29 -0400 Received: from verein.lst.de ([213.95.11.211]:50373 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726596AbgETPb0 (ORCPT ); Wed, 20 May 2020 11:31:26 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 69DAB68BEB; Wed, 20 May 2020 17:31:23 +0200 (CEST) Date: Wed, 20 May 2020 17:31:23 +0200 From: Christoph Hellwig To: Jens Axboe Cc: Christoph Hellwig , Ming Lei , linux-kernel@vger.kernel.org, Thomas Gleixner , linux-block@vger.kernel.org, John Garry , Bart Van Assche , Hannes Reinecke , io-uring@vger.kernel.org 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 Message-ID: <20200520153123.GA2340@lst.de> References: <20200518131634.GA645@lst.de> <20200518141107.GA50374@T590> <20200518165619.GA17465@lst.de> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <448d3660-0d83-889b-001f-a09ea53fa117@kernel.dk> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 20, 2020 at 09:20:50AM -0600, Jens Axboe wrote: > Just checked, and it works fine for me. If I create an SQPOLL ring with > SQ_AFF set and bound to CPU 3, if CPU 3 goes offline, then the kthread > just appears unbound but runs just fine. When CPU 3 comes online again, > the mask appears correct. > > So don't think there's anything wrong on that side. The affinity is a > performance optimization, not a correctness issue. Really not much we > can do if the chosen CPU is offlined, apart from continue to chug along. Ok, that sounds pretty sensible.