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=-7.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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 5009DC433E5 for ; Fri, 19 Mar 2021 18:47:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2BD7A61993 for ; Fri, 19 Mar 2021 18:47:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230461AbhCSSqc (ORCPT ); Fri, 19 Mar 2021 14:46:32 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:49891 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231156AbhCSSpm (ORCPT ); Fri, 19 Mar 2021 14:45:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1616179541; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SdmxWGzxufcwWyjjYxabsNbrn19FCdke2WD/CLhxr6c=; b=TGdCDAN1RWTYnfBXLK297VqS64EUYwHVvq5CK2/t6UXP4t1m5zwy5p7cwLk7+D7bP1uV+9 RgusIoLqRqp+gOGovpDldakLoDQP4hF4TOK90IRFXAXacUL/ZYc9jf8GKL/+2ln4rMxyx4 99tNwCBstWJri0ptW1vjfdbGv279e2Y= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-381-aCE7k6srPgG9D8BTDkraIQ-1; Fri, 19 Mar 2021 14:45:39 -0400 X-MC-Unique: aCE7k6srPgG9D8BTDkraIQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E8B84180FCA8; Fri, 19 Mar 2021 18:45:37 +0000 (UTC) Received: from localhost (unknown [10.18.25.174]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 447995D6D5; Fri, 19 Mar 2021 18:45:30 +0000 (UTC) Date: Fri, 19 Mar 2021 14:45:30 -0400 From: Mike Snitzer To: Ming Lei Cc: Jens Axboe , linux-block@vger.kernel.org, Christoph Hellwig , Jeffle Xu , dm-devel@redhat.com Subject: Re: [RFC PATCH V2 00/13] block: support bio based io polling Message-ID: <20210319184529.GB10212@redhat.com> References: <20210318164827.1481133-1-ming.lei@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210318164827.1481133-1-ming.lei@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Thu, Mar 18 2021 at 12:48pm -0400, Ming Lei wrote: > Hi, > > Add per-task io poll context for holding HIPRI blk-mq/underlying bios > queued from bio based driver's io submission context, and reuse one bio > padding field for storing 'cookie' returned from submit_bio() for these > bios. Also explicitly end these bios in poll context by adding two > new bio flags. > > In this way, we needn't to poll all underlying hw queues any more, > which is implemented in Jeffle's patches. And we can just poll hw queues > in which there is HIPRI IO queued. > > Usually io submission and io poll share same context, so the added io > poll context data is just like one stack variable, and the cost for > saving bios is cheap. > > Any comments are welcome. I really like your approach and am very encouraged by the early results Jeffle has shared. Please review my various nits for your next iteration of this patchset. But I think you aren't far from these changes being ready to make the 5.13 merge, which is really pretty awesome. Outstanding job Ming, thanks so much for taking on this line of work! Mike