From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tcrugnale@sandvine.com>
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134])
 by dpdk.org (Postfix) with ESMTP id BE83E902
 for <dev@dpdk.org>; Wed, 28 Oct 2015 17:46:30 +0100 (CET)
Received: from BLR-EXCHP-2.sandvine.com (192.168.196.172) by
 wtl-exchp-1.sandvine.com (192.168.194.178) with Microsoft SMTP Server (TLS)
 id 14.3.195.1; Wed, 28 Oct 2015 12:46:29 -0400
Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by
 blr-exchp-2.sandvine.com ([fe80::6c6d:7108:c63c:9055%14]) with mapi id
 14.03.0181.006; Wed, 28 Oct 2015 12:46:29 -0400
From: Tom Crugnale <tcrugnale@sandvine.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: Support for configuring MTU on i40e
Thread-Index: AdERnsxxfZKS2yvrTLWTSX4WO7Rngg==
Date: Wed, 28 Oct 2015 16:46:28 +0000
Message-ID: <9689034CEF26614CAB4B447EEAAF98E918241A27@wtl-exchp-1.sandvine.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.200.43]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] Support for configuring MTU on i40e
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: Wed, 28 Oct 2015 16:46:31 -0000

Hi,

I am trying to configure the MTU through rte_eth_dev_set_mtu() on an i40e i=
nterface and noticed that the function pointer inside of the rte_eth_dev st=
ruct for mtu_set is not populated from the i40e code.
It seems that the only API that will allow for restricting the MTU is to ca=
ll rte_eth_dev_configure() with the max_rx_pkt_len field set appropriately =
inside of the passed rte_eth_conf structure.

This makes it a bit awkward from any code that is common for all NIC types,=
 forcing the caller to fall back on rte_eth_dev_configure() when rte_eth_de=
v_set_mtu() returns -ENOTSUP.

Is there any reason why an implementation for setting the MTU isn't support=
ed through the proper API here?

Thanks,
Tom