Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp2296401ybg; Thu, 30 Jul 2020 16:12:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzNPDA4OSjaHz5Mdj4f7qYN7gfTir25JXTYK8WagtQvJ+VpmWrHs3a329TNJYjSX3UPZvfn X-Received: by 2002:aa7:c983:: with SMTP id c3mr1241751edt.383.1596150723731; Thu, 30 Jul 2020 16:12:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596150723; cv=none; d=google.com; s=arc-20160816; b=acNu2fuSYhiEVYeyTht/KR/oUkIHDiQcHU5fSAXR+Zva2k1nIRPzqsMSgBV8rx6/4z gndx1FVFVHaa2kAGVHMWIF989+B4e6UJgMdNvqkFAEamTuTVjEdGvRcpZ2elBUBTX7Pq omnxjpM4JC0UURBZL3szCbrc5p7fGTI+10bTaJeCuTb82JsOWo86UxgvE+Aj4PQsbaWX Hn254FOiUatXjzGrtyVlmkq6xgIWYgiSCWyFyCx5I4n/L9xQ2+6wwit+tzmkjLuEUMtj fEF6Iqx5CoQd1dOAe1+5yLcLH6b1kzzHBzvPn6amYyQtTHWj20JnebPFRdVQYkRVz910 ucBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=WjSBU/WTh3bay+OHzTOMY+wcHTT153GK3BmWwl9bqbE=; b=NxyQ8nrfF3KYqdKVcvPCs0kqCuQpgeAq/1eTJ3ANS+wz/JyELqJ4SVP9geDUPAVsN2 YXZja+COSDyJFuhUZ2x3c9CmzCW0A4uMFBUiepRESjDDY9qLqN2kHlgnPbZkIkEph1ta QIx0Yd7dkbkVJhDGx2hatwx08aZ1n0pVn+3X8Qx326GQKtJKoTAoRX152u2mEdtA3jHg qG510q3CSYfdAwd4PoV1rhCYK2SUnZxQxXwQOo8UyTemLz8mjS4F+8uXoW55zGAX/fZo zX5K9HmRNgA3TWpHCCpNCNjQv5kKs+FqewcKFqrle7L5S9Lurik2C/QjpEEskuTumspr 5QPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=yKMAJx19; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id od24si3797751ejb.321.2020.07.30.16.11.21; Thu, 30 Jul 2020 16:12:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=yKMAJx19; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730543AbgG3XLE (ORCPT + 99 others); Thu, 30 Jul 2020 19:11:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:53170 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728588AbgG3XLD (ORCPT ); Thu, 30 Jul 2020 19:11:03 -0400 Received: from kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com (unknown [163.114.132.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DAE4020809; Thu, 30 Jul 2020 23:11:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596150663; bh=d7EuQ0AAcl/JAtg15EpS6qwrrRhGuijEjeshu+bi+fQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=yKMAJx19arwhG8RMKjMSXZm20W5syYg2r9Vfi5N5havOQGeHUQ0zxA6h+j/rEJYdH xZH2sLoG8q8tRRYG6pQ8qa/bDOapthREjYdv+uodN7gaLgpudBs065yAV/57MLiQda E/YRl27bjYeYXfOi/qIT8O7fVCLPYDJnyoTBT+0I= Date: Thu, 30 Jul 2020 16:11:01 -0700 From: Jakub Kicinski To: Moshe Shemesh Cc: Jacob Keller , Jiri Pirko , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" , Jiri Pirko , Vasundhara Volam Subject: Re: [PATCH net-next RFC 01/13] devlink: Add reload level option to devlink reload command Message-ID: <20200730161101.48f42c5b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> In-Reply-To: <3352bd96-d10e-6961-079d-5c913a967513@mellanox.com> References: <1595847753-2234-1-git-send-email-moshe@mellanox.com> <1595847753-2234-2-git-send-email-moshe@mellanox.com> <20200727175802.04890dd3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20200728135808.GC2207@nanopsycho> <464add44-3ab1-21b8-3dba-a88202350bb9@intel.com> <20200728114458.762b5396@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20200728130653.7ce2f013@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <04f00024-758c-bc19-c187-49847c24a5a4@mellanox.com> <20200729140708.5f914c15@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <3352bd96-d10e-6961-079d-5c913a967513@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Jul 2020 15:30:45 +0300 Moshe Shemesh wrote: > >>> My expectations would be that the driver must perform the lowest > >>> reset level possible that satisfies the requested functional change. > >>> IOW driver may do more, in fact it should be acceptable for the > >>> driver to always for a full HW reset (unless --live or other > >>> constraint is specified). > >> OK, but some combinations may still not be valid for specific driver > >> even if it tries lowest level possible. > > Can you give an example? > > For example take the combination of fw-live-patch and param-init. > > The fw-live-patch needs no re-initialization, while the param-init > requires driver re-initialization. > > So the only way to do that is to the one command after the other, not > really combining. You need to read my responses more carefully. I don't have fw-live-patch in my proposal. The operation is fw-activate, --live is independent and an constraint, not an operation.