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=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 D7FC4C43331 for ; Thu, 2 Apr 2020 16:28:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A414F206F6 for ; Thu, 2 Apr 2020 16:28:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=cloud.ionos.com header.i=@cloud.ionos.com header.b="cyAtrTVx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389041AbgDBQ2C (ORCPT ); Thu, 2 Apr 2020 12:28:02 -0400 Received: from mail-il1-f175.google.com ([209.85.166.175]:46516 "EHLO mail-il1-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731892AbgDBQ2B (ORCPT ); Thu, 2 Apr 2020 12:28:01 -0400 Received: by mail-il1-f175.google.com with SMTP id i75so4160484ild.13 for ; Thu, 02 Apr 2020 09:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloud.ionos.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+LWQRzvGUf0Noo8gQmhIsnF90MWgcXs+EjcH83IaZZI=; b=cyAtrTVxn8FFy1qj++2UDFQvNzskVPe9VtPrHb+clKTiQLHHTU7tnza2uSu0zk2FMB QQxzhOvv99qOh2WZfAaUZM5I8TR7QgTxWA3Vy7e6s1UZ/lyxX70FbQ+Te56n0awso5na Nnqii4V9Rvu2TeK/7ZT1EgLkDsa0TDBdp9LEe20Pv8j3yuOxKxwwNZEP7JU2kjAl7/EN qgTizy2VhBStl+hR3noLJhwKet8yeXuqRSqntRO4Gqx90IDDnWiVm8QCnIn5WNczDXmK wsp+sFaam7gmn0IyAFw5t8qzz+ogRRPlJodVPDvDSGNzNbR1avKF8PwshzpV7OXS5oAA 0iqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+LWQRzvGUf0Noo8gQmhIsnF90MWgcXs+EjcH83IaZZI=; b=KW3QvE9EVTGxE84bMr9ePueklfaemTsdn8el58Pbmtc5ZrVrC3j9SYc6+HxBm40gUd kgEMHtsBOzqsNbzhSt3hxd05B+Ue54HOKmRzSi6hYAXA49sG12MZEssRZxvJT35EdrAE kgqguXNhGkOtAS78F1S8ytFL5k8VfKnzQvR8UUJtmfL00sOpJ2YwKGK3chodyYKxmvqr SwDHLFsrQ46Z65XN8savta+3cvfNubdEDa5DAFS5KAn3v7h4w64MX+ge4R2r/EVHNA2L y3ioB2GWnD6AgMmCEI8xHepUDkBvV7JvM7iLRKyqtOWyVtbZyBoreCGciY3ylEXWN8Yl wDBQ== X-Gm-Message-State: AGi0PuZlt6D+ogyBulKRHiVdVG/ezFgtOI7GmbuilENxwWVNI+yhqWs5 L+UjD+kBZ9qH8LEQa//FP4mkOCN7qXsof39Z7VFweg== X-Google-Smtp-Source: APiQypIsUTohrvKHniCIy83q9ah4PZqWdPsXTTnRHexEKhHjSG91k73rGGZj9Uezdib+zAGJMz9OH6yGZwu43ziQb2A= X-Received: by 2002:a92:8159:: with SMTP id e86mr3907587ild.60.1585844880822; Thu, 02 Apr 2020 09:28:00 -0700 (PDT) MIME-Version: 1.0 References: <20200320121657.1165-1-jinpu.wang@cloud.ionos.com> <20200320121657.1165-19-jinpu.wang@cloud.ionos.com> <198cd2da-cbf8-17b0-3ee5-5dec366a43e2@acm.org> In-Reply-To: From: Jinpu Wang Date: Thu, 2 Apr 2020 18:27:50 +0200 Message-ID: Subject: Re: [PATCH v11 18/26] block/rnbd: client: main functionality To: Bart Van Assche Cc: linux-block@vger.kernel.org, linux-rdma@vger.kernel.org, Jens Axboe , Christoph Hellwig , Sagi Grimberg , Leon Romanovsky , Doug Ledford , Jason Gunthorpe , Danil Kipnis , Roman Penyaev , Pankaj Gupta Content-Type: text/plain; charset="UTF-8" Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org > > Would it be possible to use the .get_budget / .put_budget callbacks for > > obtaining / releasing a "permit" object? I'm asking this because it was > > really tricky to get the .get_budget / .put_budget calls right in the > > block layer core. See also commit 0bca799b9280 ("blk-mq: order getting > > budget and driver tag") # v4.17. > > Will check if we can use .get_budget/put_budget call back. I checked get_budget/put_budget only has single parameter blk_mq_hw_ctx, so it's not possible save the permit for later to release/put back the permit. Thanks!