From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Kicinski Subject: Re: [RFC PATCH net-next v2 00/17] ethtool netlink interface (WiP) Date: Mon, 30 Jul 2018 17:38:43 -0700 Message-ID: <20180730173843.797f59e0@cakuba.netronome.com> References: <20180730130747.GH2058@nanopsycho> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Michal Kubecek , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, David Miller , Florian Fainelli , Roopa Prabhu , "John W. Linville" To: Jiri Pirko Return-path: Received: from mx4.wp.pl ([212.77.101.11]:25857 "EHLO mx4.wp.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726622AbeGaCXG (ORCPT ); Mon, 30 Jul 2018 22:23:06 -0400 In-Reply-To: <20180730130747.GH2058@nanopsycho> Sender: netdev-owner@vger.kernel.org List-ID: 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.