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;
Date:   Mon, 30 Jul 2018 17:38:43 -0700
From:   Jakub Kicinski <kubakici@wp.pl>
To:     Jiri Pirko <jiri@resnulli.us>
Cc:     Michal Kubecek <mkubecek@suse.cz>, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Roopa Prabhu <roopa@cumulusnetworks.com>,
        "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [RFC PATCH net-next v2 00/17] ethtool netlink interface (WiP)
Message-ID: <20180730173843.797f59e0@cakuba.netronome.com>
In-Reply-To: <20180730130747.GH2058@nanopsycho>
References: <cover.1532953989.git.mkubecek@suse.cz>
        <20180730130747.GH2058@nanopsycho>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 30 Jul 2018 15:07:47 +0200, Jiri Pirko wrote:
> >- find reasonable format for data transfers (e.g. eeprom dump or flash);
> >  I don't have clear idea how big these can get and if 64 KB limit on
> >  attribute size (including nested ones) is a problem; if so, dumps can
> >  be an answer for dumps, some kind of multi-message requests would be
> >  needed for flashes  
> 
> This is another thing that should go into devlink as it is not
> netdev-handled. We have now a "region" facility there which can be
> re-used.

+1 regions should cover the current use cases and are a better API IMHO.