Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2575623rwd; Fri, 16 Jun 2023 05:42:09 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6UtJSYS/JVQeTElfqoxQBOdtEMgE7sfNRz3dXTXy7MpOnDjnnBFXw074xqLY2huXvXxbWr X-Received: by 2002:a17:90b:350f:b0:258:d367:63c with SMTP id ls15-20020a17090b350f00b00258d367063cmr2176194pjb.1.1686919329062; Fri, 16 Jun 2023 05:42:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686919329; cv=none; d=google.com; s=arc-20160816; b=PLH774G3d+LEllYajBRaYb9vxqrUGY8NM8DNjDMa2gGjIW5DcI0f1ZTTgGGi33ezmd W5KCrMyAkrZn2YM1Khms6+Oh5gP67nDARQRhpf9pTJICLhZYSc1Zi4yIx7xFmHKuCFjA IPKMgJKgdVHgqkuU6WLpQX1jzlSPejd/zH0y2r+KPrUescbKPrhSP2tLf+jjqGdvEC9E 0UmoO3wTR7LciOIQy5pj+CnDsUVBqUf/Re7RyzLcTNUh0uCyKhrBLMmCPEfKpFtKnR5G Vn8Havs3B6ArXm/tX0jIWjaM+e5MH/PVNSNZ6JCY8vCPEi5cWNICdYf4GLotlVjRF2If va+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=j2xfXHpjBMvteDK7gwHfYuLl3yobwBo2x/lHNADmH3A=; b=XN7YMUTwJyWkDLUTqvSmcAnvBXlDrv7LGQG5nbQNuIwxc5Ce6loiVkEQn04ouHvmqG p53Ct7bF8FunUf2NZg5WU2dV34g+927vE3RDfFqt3a4P2UCZHphbQmfwpckU+dJDJ3Nl Bal3+RGN5XsR4fM4LVCh9Abs1YvS4+ONgneDNSxkXbN2WgMfcUF1i0Rz5sGum9kuJivR FmeX1ibK7/6vWTsc7wM3IapL8YKkwLYwQKVg9jwSIBZ7JqqPZYoIpsUXb0LhBkL0eiU0 9Jp0PifAwr98e3c1IM0qqMisysmdgIZWv2H7W3gY9Wnwbhvi0xvqzG61fcTDU0Drvc2f 0l8g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u1-20020a17090a410100b00256c6c76723si1484580pjf.69.2023.06.16.05.41.18; Fri, 16 Jun 2023 05:42:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344540AbjFPMXK (ORCPT + 99 others); Fri, 16 Jun 2023 08:23:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60528 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344622AbjFPMXI (ORCPT ); Fri, 16 Jun 2023 08:23:08 -0400 Received: from 167-179-156-38.a7b39c.syd.nbn.aussiebb.net (167-179-156-38.a7b39c.syd.nbn.aussiebb.net [167.179.156.38]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0414730F2 for ; Fri, 16 Jun 2023 05:23:04 -0700 (PDT) Received: from loth.rohan.me.apana.org.au ([192.168.167.2]) by formenos.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1qA8Ti-003oWp-Qm; Fri, 16 Jun 2023 20:22:59 +0800 Received: by loth.rohan.me.apana.org.au (sSMTP sendmail emulation); Fri, 16 Jun 2023 20:22:58 +0800 Date: Fri, 16 Jun 2023 20:22:58 +0800 From: Herbert Xu To: Damian Muszynski Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com, Giovanni Cabiddu Subject: Re: [PATCH] crypto: qat - add internal timer for qat 4xxx Message-ID: References: <20230601091340.12626-1-damian.muszynski@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=2.7 required=5.0 tests=BAYES_00,HELO_DYNAMIC_IPADDR2, PDS_RDNS_DYNAMIC_FP,RDNS_DYNAMIC,SPF_HELO_NONE,SPF_PASS,TVD_RCVD_IP, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Fri, Jun 09, 2023 at 02:04:24PM +0200, Damian Muszynski wrote: > > We considered the usage of delayed work when implementing this, but it will > break functionality. Apart from scheduling the work queue, timer_handler() is > incrementing a counter which keeps track of how many times the timer was scheduled. Please be more specific. I don't understand why the counter can't be incremented in the delayed work instead of the timer. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt