DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tom Crugnale <tcrugnale@sandvine.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Support for configuring MTU on i40e
Date: Wed, 28 Oct 2015 16:46:28 +0000	[thread overview]
Message-ID: <9689034CEF26614CAB4B447EEAAF98E918241A27@wtl-exchp-1.sandvine.com> (raw)

Hi,

I am trying to configure the MTU through rte_eth_dev_set_mtu() on an i40e interface and noticed that the function pointer inside of the rte_eth_dev struct 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 call 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_dev_set_mtu() returns -ENOTSUP.

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

Thanks,
Tom

                 reply	other threads:[~2015-10-28 16:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9689034CEF26614CAB4B447EEAAF98E918241A27@wtl-exchp-1.sandvine.com \
    --to=tcrugnale@sandvine.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).