Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2552454imm; Tue, 4 Sep 2018 06:28:05 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZVS1oKfyI9WP3ugeyhVahJcAwxZa51Y2kDBA8nz/86KnE8IRrJeBckMamt4HVp16jxZ54l X-Received: by 2002:a63:6446:: with SMTP id y67-v6mr31405775pgb.443.1536067685289; Tue, 04 Sep 2018 06:28:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536067685; cv=none; d=google.com; s=arc-20160816; b=HCgx8LbYv7D/+/54BNfku2QFYgklF1AvJpdUhtitwW57vzFQhvcWtxGWnU7sgM0H/c 3mtL5No5lT1HRJKPDrZQ9lvcFm0oHGQpVYvBeL4p17ihsbWp8YLeXXvWOaW+wNV/3fft v03dDMVVIDf5RgwQXhs9h+xEcNDZJJ7p467QfigtiTbqutyltHubQgaSip5i1J4l2PAa 90aT0ogIs7QITsNk0xL03j8fZ9FIRHuFj6eVsGuBxVGxjMvtPqNBhnc2NslNOXLZ0C/j jJSzYdkOHHKI5bHX4ntnXDBzjYLxn0cJ6H7k0iSHu0kwiqqjEaLqlproqhT/t3MMWzIC NI9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=v1iQqBBewQi1qC/zDOOyAZ4LSiZoUncm/h32M5L6IWM=; b=eqQQrYygNcy/pYkIWw27p4Z4RJ32rZo2LO68rFzKUr4UejnojIshsyhJsVNNMQolZr 1VAEHlyTP4BglPvHEOiDMerplNY6+47bqGdDHYf4hiISPxJx9tcZy1/fCz+9da+QDmDk vKNpPxYpMm0pdv1Sz0lY5Xvhb3U+L+lkjxZGF4Y/cunVo0DlDjQLlN3PVXnZDMyDCxg+ wVdQb3TBIQXkoqadW8W7Ex5AMudIyjY+52pO5SPARPnd+fBRw1Snx0g86+qii7pHC8ZU CLNh61WT839uxlL8GR46u9mtDMWfSbQaQBkimPqFuWRSwe7JMmjuxnfRKsv7ksTUvc3x Ol9A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x32-v6si20990947pld.330.2018.09.04.06.27.50; Tue, 04 Sep 2018 06:28:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727335AbeIDRvr (ORCPT + 99 others); Tue, 4 Sep 2018 13:51:47 -0400 Received: from verein.lst.de ([213.95.11.211]:40801 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726208AbeIDRvr (ORCPT ); Tue, 4 Sep 2018 13:51:47 -0400 Received: by newverein.lst.de (Postfix, from userid 2005) id C438168D40; Tue, 4 Sep 2018 15:30:06 +0200 (CEST) Date: Tue, 4 Sep 2018 15:30:06 +0200 From: Torsten Duwe To: "Martin K. Petersen" Cc: herbert@gondor.apana.org.au, Jeff.Lien@wdc.com, ard.biesheuvel@linaro.org, david.darrington@wdc.com, hch@infradead.org, jeff.furlong@wdc.com, linux-block@vger.kernel.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, tim.c.chen@linux.intel.com Subject: Re: [PATCH v2 1/3] crypto: Introduce notifier for new crypto algorithms Message-ID: <20180904133006.GA28715@lst.de> References: <20180827060918.tfz7ljufqhlej4kq@gondor.apana.org.au> <20180830150016.15661-1-martin.petersen@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180830150016.15661-1-martin.petersen@oracle.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 30, 2018 at 11:00:14AM -0400, Martin K. Petersen wrote: > Introduce a facility that can be used to receive a notification > callback when a new algorithm becomes available. This can be used by > existing crypto registrations to trigger a switch from a software-only > algorithm to a hardware-accelerated version. While this is apparently fine with the patch set you sent, what about cases where the crypto context of old and new implementation is not 100% compatible? The switch will still work for sure if there are no current active users of the algo, but otherwise...? Just a thought. Torsten