From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C47AC47082 for ; Tue, 8 Jun 2021 05:26:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1E6886101A for ; Tue, 8 Jun 2021 05:26:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229512AbhFHF2e (ORCPT ); Tue, 8 Jun 2021 01:28:34 -0400 Received: from verein.lst.de ([213.95.11.211]:49151 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230160AbhFHF2e (ORCPT ); Tue, 8 Jun 2021 01:28:34 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id EC1E267373; Tue, 8 Jun 2021 07:26:39 +0200 (CEST) Date: Tue, 8 Jun 2021 07:26:39 +0200 From: Christoph Hellwig To: Keith Busch Cc: Kanchan Joshi , linux-nvme@lists.infradead.org, Sagi Grimberg , Christoph Hellwig , Jens Axboe , linux-block@vger.kernel.org, Yuanyuan Zhong , Casey Chen , Ming Lei Subject: Re: [PATCHv3 2/4] nvme: use blk_execute_rq() for passthrough commands Message-ID: <20210608052639.GC13828@lst.de> References: <20210521202145.3674904-1-kbusch@kernel.org> <20210521202145.3674904-3-kbusch@kernel.org> <20210607161512.GB21631@redsun51.ssa.fujisawa.hgst.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210607161512.GB21631@redsun51.ssa.fujisawa.hgst.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Tue, Jun 08, 2021 at 01:15:12AM +0900, Keith Busch wrote: > > The new code doesn't retain this flag. > > Looks good otherwise. > > The flag is only used to select an apporpriate hctx. We've explicitly > selected a polling hctx in this path already, so the flag is > unnecessary. I think setting the flag would still be useful, if only to prevent issues with new callers and/or better document what we are doing.