From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vincent.jardin@6wind.com>
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com
 [209.85.212.182]) by dpdk.org (Postfix) with ESMTP id 95DB8B0B6
 for <dev@dpdk.org>; Mon,  2 Jun 2014 23:35:04 +0200 (CEST)
Received: by mail-wi0-f182.google.com with SMTP id r20so5383167wiv.3
 for <dev@dpdk.org>; Mon, 02 Jun 2014 14:35:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:organization:user-agent
 :mime-version:to:cc:subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=rtj/QGxpI8EPHisj1h3B+4VCCaIyPm5/7CV841bEb6g=;
 b=U/H2pFvqmZrOSYgLRQ9Cz6mFHMY6xwLP6mhqHr7nm1YPIDJCndPs+ujERcSayYa3u0
 xpO0cJE8GJYpf9VWRLD4c8gzO7G7hzNuNTVjmTL5FNoFFHmssB0R5sSjfaPEX6/TTlCA
 1XAjPuYrOZp6priAZ0WGQny1ROmhgNJkijEF+GaWb1t31Y66bQ6HCRGMeF8Pz7UiaNke
 MvynY4w+jP7cXrtTGWNz6y5xLc9OlBqOcqo97QPtomXu7rY92ZxShCaxvhfs0hGc5utP
 sTX5u4bNV5RbIqHVvOIaCW7t8HUzINdr6C4AmkYqfjEpb4cTD1BG7sukGe9stohHq2WG
 6Zog==
X-Gm-Message-State: ALoCoQlpYW9aRSlZicAdv+1kYaClKavkvu3yonjjCePAgk157tD+9CC2inEuHuU5exD61c+IuFgF
X-Received: by 10.194.110.71 with SMTP id hy7mr53682837wjb.23.1401744914848;
 Mon, 02 Jun 2014 14:35:14 -0700 (PDT)
Received: from saturne.dev.6wind.com ([2a01:e35:8a8e:1b70:226:b9ff:fec7:e133])
 by mx.google.com with ESMTPSA id
 b19sm35817414wic.5.2014.06.02.14.35.13 for <multiple recipients>
 (version=TLSv1 cipher=RC4-SHA bits=128/128);
 Mon, 02 Jun 2014 14:35:13 -0700 (PDT)
Message-ID: <538CEE10.4000900@6wind.com>
Date: Mon, 02 Jun 2014 23:35:12 +0200
From: Vincent JARDIN <vincent.jardin@6wind.com>
Organization: www.6wind.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: dev@dpdk.org
References: <CAAJNys+ZkPdnZaN58d+FMf75vcKJTWenWvHLBXCSBjzY0WFZ4w@mail.gmail.com>
 <5D695A7F6F10504DBD9B9187395A21797D0CF42B@ORSMSX112.amr.corp.intel.com>
 <CAAJNysKzUt1KtzQVj0_rQtDPBfjKi=jYmyb57xU3OxdAS1wE3A@mail.gmail.com>
 <20140602203735.GL8384@x220.localdomain>
In-Reply-To: <20140602203735.GL8384@x220.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hyunseok@ieee.org
Subject: Re: [dpdk-dev] Ethtool support in DPDK pmd
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2014 21:35:04 -0000

On 02/06/2014 22:37, Chris Wright wrote:
> If drivers stayed in kernel and kernel drivers exposed a mechansim for
> registering application dma buffers for dpdk apps, then ethtool would
> simply work as-is.

Yes, that's the right way to go. Currently, the kernel does not provide 
a generic framework for that and I am not aware of any projects in order 
to define it. Could it be something to discuss on netdev@?

So, as a workaround, some proprietary solutions get implemented in order 
to get ethtool running with any DPDK PMD.

Best regards,
   Vincent