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=-12.6 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=unavailable 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 95EF7C433DB for ; Wed, 27 Jan 2021 17:16:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 55D9664DAA for ; Wed, 27 Jan 2021 17:16:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235034AbhA0RQR (ORCPT ); Wed, 27 Jan 2021 12:16:17 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:22853 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234128AbhA0RO4 (ORCPT ); Wed, 27 Jan 2021 12:14:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1611767607; 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=Z7mGBlHRLZU/PRglXzorkWK1u2MHkwHlUmIrHobRuLA=; b=B1dTFyOz7kFDglXJQhJNb5z2T0sFzDG/+BCglBO8Jj8plprlfFGh1UxTjsuLHssTKYAeZP rmT2NtQ7t24Dv8sesnatGst0GCJCYC/4JY+Uu0gl9fvjknOQf3ZoduKu12cwPYZxpwrnGJ P0lMFz3Q5K7C/bclJ5l+qn2siAjjYNs= 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-558-1z67nAIJOyGQ97FrMb-vSA-1; Wed, 27 Jan 2021 12:13:26 -0500 X-MC-Unique: 1z67nAIJOyGQ97FrMb-vSA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0DDA98145E0; Wed, 27 Jan 2021 17:13:25 +0000 (UTC) Received: from localhost (unknown [10.18.25.174]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BDBB660873; Wed, 27 Jan 2021 17:13:21 +0000 (UTC) Date: Wed, 27 Jan 2021 12:13:21 -0500 From: Mike Snitzer To: Jeffle Xu Cc: joseph.qi@linux.alibaba.com, dm-devel@redhat.com, linux-block@vger.kernel.org, io-uring@vger.kernel.org Subject: Re: [PATCH v2 5/6] block: add QUEUE_FLAG_POLL_CAP flag Message-ID: <20210127171320.GA11535@redhat.com> References: <20210125121340.70459-1-jefflexu@linux.alibaba.com> <20210125121340.70459-6-jefflexu@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210125121340.70459-6-jefflexu@linux.alibaba.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Mon, Jan 25 2021 at 7:13am -0500, Jeffle Xu wrote: > Introduce QUEUE_FLAG_POLL_CAP flag representing if the request queue > capable of polling or not. > > Signed-off-by: Jeffle Xu Why are you adding QUEUE_FLAG_POLL_CAP? Doesn't seem as though DM or anything else actually needs it. Mike