Received: by 2002:a05:7412:3290:b0:fa:6e18:a558 with SMTP id ev16csp628376rdb; Fri, 26 Jan 2024 06:13:28 -0800 (PST) X-Google-Smtp-Source: AGHT+IEyeQs0HjBayxz/lCMKU2tC8kL+sjT0VhyPyvKatbiVovUMviL7fhMgoB5p2G1lQNNlAYF3 X-Received: by 2002:a17:902:dacd:b0:1d7:17e6:44fb with SMTP id q13-20020a170902dacd00b001d717e644fbmr1537443plx.32.1706278407895; Fri, 26 Jan 2024 06:13:27 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706278407; cv=pass; d=google.com; s=arc-20160816; b=1ACUuNGSKsGPDr4iylElstBbuvfhB3ZCcP4eyLVLQaCYMBt41yR0hKQexZ/BR47YBb 5JcYda8v20pY4Du2PnJmkbFrXG7sLW45cjWaLFNau1Qtzqm+n5LsEz3Wi7lCXiyeQyTw /NYB1vYB959GVYtYlkE0VIqz6oLcAQide3Yer5PE05mP0Cyhg8BBr++VawK1KA41PTmZ URYRaTORIa4nZdiZrAuD5taUabptKjQnr/eXErEvgN2AOZ7HKRCbUvgYUqB6UsitKfAZ BYH6doQ95ty3wIdPiAwhdj05VX5c15cbQvoc4bu2uBUuN/jg6H/Gm1eS9D/OyOOWbjab rfnw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version :list-unsubscribe:list-subscribe:list-id:precedence:references :message-id:subject:cc:to:from:date; bh=J7GM5aCwzj+ZhbzMfZPkOXnZG2N7cwwosfVTElAtH5Y=; fh=yJsCquabS1/5DGxttPUtVdlF+UJ+F92cHyb0qO0Dow4=; b=CeLwcb7EZnXkJ8ZoZRYRqeDapA9aLONITWzzxlUUy91oE7mqEitbBgjIJGWyxg5s1y Qn56568Mx5XpKo782R0YO4HLRGK7Nf7T+Dzi8smt+wobav0SKgBk1VaX99f0EClsf0rO m6sG43kST28KJ9Meg1SLQN4QxAR3icFQWtwIkuoRTDlB1OB1Auw9jUuM8voFMV15GXua ZMq8QK6hNN20P+Fg5RO32xB7naY4UJU8mWWJgf5u4YzBpIbNmvFvZ2wIsuZJFz4dhkaC SN+s2Y7SbvhEmyvpRq6mHPZSOU3XON2+L1tEmKdd79xUjjtoV8MGhQcFuIQ1ERm5xUhT oqNw== ARC-Authentication-Results: i=2; mx.google.com; arc=pass (i=1 spf=pass spfdomain=lst.de); spf=pass (google.com: domain of linux-kernel+bounces-40145-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40145-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id u71-20020a63854a000000b005c701bf0e27si1170646pgd.79.2024.01.26.06.13.27 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jan 2024 06:13:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-40145-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; arc=pass (i=1 spf=pass spfdomain=lst.de); spf=pass (google.com: domain of linux-kernel+bounces-40145-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40145-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 5F592284A65 for ; Fri, 26 Jan 2024 13:52:40 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 652CA1B963; Fri, 26 Jan 2024 13:52:31 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2457D1B943; Fri, 26 Jan 2024 13:52:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706277150; cv=none; b=N0PawXoUB8zodY0Emo2s9uUH70h6EQj8EDRf3kv/5RomubCzHc7bNOqeoZOgLGJU+zF6OG96LSKVmLZVUSCrR8NdDPp/4kv3F1gPfquaaX4dzD9u1Jx+zLaQifYRIkAhZTy/B+5cfKFJOJZXF3rwkB6ZwCwn7yFQawojlQmeHvg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706277150; c=relaxed/simple; bh=oEds4qWCVxolYDA+yZojD2fii414dNCAA09U6ZafQ+I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=DLOZvM5dly0wac+B4URb6cH9/5ftUEQ6Dplefqumy8ZitcaQrkv+yUkAJW/gWF/CgdfNzz73zzvMeYCCcJa1SGCyVLpAKaGImZOfkhgY9EM+QvEHnZKESKe+YYEwt2CZtPYYoL9h9ZZMaeJBbi2LH8q1ce45xoAgtPUzQ/QpqNE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id E935B68C4E; Fri, 26 Jan 2024 14:52:24 +0100 (CET) Date: Fri, 26 Jan 2024 14:52:24 +0100 From: Christoph Hellwig To: Jens Axboe Cc: Matthew Wilcox , Christoph Hellwig , linux-block@vger.kernel.org, tj@kernel.org, jiangshanlai@gmail.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH, RFC] block: set noio context in submit_bio_noacct_nocheck Message-ID: <20240126135224.GA3368@lst.de> References: <20240124093941.2259199-1-hch@lst.de> <20240125081050.GA21006@lst.de> <07de550c-2048-4b2f-8127-e20de352ffde@kernel.dk> <6c4a4cf3-c5ed-4236-a6b2-9d53e927f979@kernel.dk> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6c4a4cf3-c5ed-4236-a6b2-9d53e927f979@kernel.dk> User-Agent: Mutt/1.5.17 (2007-11-01) On Thu, Jan 25, 2024 at 09:13:37AM -0700, Jens Axboe wrote: > > Nono, you don't understand. The plan is to remove GFP_NOIO > > entirely. Allocations should be done with GFP_KERNEL while under a > > memalloc_noio_save(). > > I do understand, but thanks for the vote of confidence. Place the > save/restore higher up, most likely actual IO submission isn't going to > be the only (or even major) allocation potentially needed for the IO. NOIO is defined as allocations that will not recurse into the I/O stack. So for anything block based, entering the block layer is literally the defined boundary where it should be used below. So no, wrapping every submit_bio into a context annotation doesn't make much sense.