Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp248770rwd; Wed, 24 May 2023 17:40:07 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4us1Bud0gov1rxRpEM82OJHAu8S7H2PMfaphTgYUtWP6QLlrpXQSlxfz5hVwvVbs+Xves4 X-Received: by 2002:a17:903:25c4:b0:1ad:f68b:f99e with SMTP id jc4-20020a17090325c400b001adf68bf99emr16110702plb.16.1684975206443; Wed, 24 May 2023 17:40:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684975206; cv=none; d=google.com; s=arc-20160816; b=SbebpYjM2YHZICQCt17ItgnxweG5BFHDDNaOUTjjQAx3qEnPtvlJGJzxb05s1xUE3i qDFHHp/TWoLWZo11tmv3XUKM3kM/9dwmiLMnct50yZ/ZRBGWzeB9ORzLqM4vbVAzURqS 7G1QIfn6rh5SSSo6vX7qNhHXVi784NJPxLN+9l//71nbWAWByOm5ByzdK2HOfWPzurdW gbY/yXjqvmVkYWEMlYRiHfbCvCsxI+vLCczUy8s/ut78VEGBhMf7xUKk+L5QmmOndQo8 q+C48R2cQ/AaRPORXZxtck+SDF6SV5Z9uKbY6HSffJR5J1ufIbtC0VdgYyGVvNgUdm04 MayA== 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=NDSNlCd6kHYnUQMShi1ATpScZ/zRCepiBIHSEm+zdrs=; b=UO/CwxlTJVdezlBXd8m210fM+uusiuZturDGuxaa7eVcTFN+1DJJqrlP8wc9J1GqHL 6mw7Z7Y6phPine8ejy4Nmcwv5lTZIuIsFsark8yCXpX0Wc+xc6+vz/yeS1QzrKyRod2+ cv+w2IaKErbIW6zOJpZvQJTZ4LSXoYh/sGhlPiQ4twbwrouqhD7ZTlakqGbHMysS5GzM /k1Oc5VgMQ2m6lXXb+OtQIgiIfyONNKNYg19DxBYsy51Dc77YUO/2tj2ppri9o3Djrfw SFMx14WgK2wt9WfaId0mXuzyGHOkvZo+TbbA9QJ2Oq/xNONMV1vOKsOD8L3RTxAkrNLi m84Q== 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 h2-20020a170902f54200b001aae5ec6ac9si118550plf.547.2023.05.24.17.39.43; Wed, 24 May 2023 17:40:06 -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 S229551AbjEYAhk (ORCPT + 99 others); Wed, 24 May 2023 20:37:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41830 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229454AbjEYAhj (ORCPT ); Wed, 24 May 2023 20:37:39 -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 CACE69B; Wed, 24 May 2023 17:37:35 -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 1q1yyg-00D229-Hg; Thu, 25 May 2023 08:37:15 +0800 Received: by loth.rohan.me.apana.org.au (sSMTP sendmail emulation); Thu, 25 May 2023 08:37:14 +0800 Date: Thu, 25 May 2023 08:37:14 +0800 From: Herbert Xu To: Tom Zanussi Cc: davem@davemloft.net, fenghua.yu@intel.com, vkoul@kernel.org, dave.jiang@intel.com, tony.luck@intel.com, wajdi.k.feghali@intel.com, james.guilford@intel.com, kanchana.p.sridhar@intel.com, giovanni.cabiddu@intel.com, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org Subject: Re: [PATCH v5 13/15] crypto: iaa - Add support for default IAA 'canned' compression mode Message-ID: References: <20230516215009.51794-1-tom.zanussi@linux.intel.com> <20230516215009.51794-14-tom.zanussi@linux.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, 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 Wed, May 24, 2023 at 10:58:54AM -0500, Tom Zanussi wrote: > > Yes, I think you're right. The reason we did it this way was that > we're expecting to add more modes, such as 'dynamic' and/or 'canned- > dynamic' etc. > > But I don't see a reason we couldn't just register them all and have > the user choose using the algorithm names, especially if that's the way > crypto users expect things to work. Are these modes compatible with the deflate algorithm, that is, can the generic deflate uncompress the output of these modes and vice versa, can these modes uncompress the output of the generic algorithm? If they're all compatible, then you should just use the "deflate" algorithm name and use different driver names to differentiate them. But if they're not compatible then the modes should have distinct algorithm names. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt