From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ian Stokes <ian.stokes@intel.com>, dev@dpdk.org
Cc: stephen@networkplumber.org
Subject: Re: [dpdk-dev] [PATCH v2 7/7] app/testpmd: verify mtu with rte_eth_dev_info_get()
Date: Mon, 25 Mar 2019 14:20:32 +0000 [thread overview]
Message-ID: <6aa38aa8-5bb3-fee1-0449-c1cc11115a67@intel.com> (raw)
Message-ID: <20190325142032._8Z-dAj1VuRHhKIRWYSqn7D8bP5WOXhDgnY9PPOBwi4@z> (raw)
In-Reply-To: <1553259678-4515-8-git-send-email-ian.stokes@intel.com>
On 3/22/2019 1:01 PM, Ian Stokes wrote:
> This commit uses the mtu fields populated in rte_eth_dev_info_get()
> to validate the mtu value being passed in port_mtu_set().
>
> Signed-off-by: Ian Stokes <ian.stokes@intel.com>
For patch title, I think 'rte_eth_dev_info_get()' is implementation detail here,
what we are verifying mtu against min/max MTU information provided by PMDs.
What do you think something like:
app/testpmd: verify MTU with PMD provided limits
> ---
> app/test-pmd/config.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
> index b9e5dd923..6ca97d0e7 100644
> --- a/app/test-pmd/config.c
> +++ b/app/test-pmd/config.c
> @@ -1063,9 +1063,13 @@ void
> port_mtu_set(portid_t port_id, uint16_t mtu)
> {
> int diag;
> + struct rte_eth_dev_info dev_info;
>
> if (port_id_is_invalid(port_id, ENABLED_WARN))
> return;
> + rte_eth_dev_info_get(port_id, &dev_info);
> + if (mtu > dev_info.max_mtu || mtu < dev_info.min_mtu)
> + return;
This fails silently, I think better to put a log for failure.
> diag = rte_eth_dev_set_mtu(port_id, mtu);
> if (diag == 0)
> return;
>
next prev parent reply other threads:[~2019-03-25 14:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 13:01 [dpdk-dev] [PATCH v2 0/7] ethdev: add min/max MTU to device info Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 1/7] " Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-25 14:26 ` Ferruh Yigit
2019-03-25 14:26 ` Ferruh Yigit
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 2/7] net/i40e: set min and max MTU for i40e devices Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 3/7] net/i40e: set min and max MTU for i40e VF devices Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 4/7] net/ixgbe: set min and max MTU for ixgbe devices Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 5/7] net/ixgbe: set min and max MTU for ixgbe VF devices Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 6/7] net/e1000: set min and max MTU for igb devices Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-25 14:25 ` Ferruh Yigit
2019-03-25 14:25 ` Ferruh Yigit
2019-03-26 13:58 ` Zhang, Qi Z
2019-03-26 13:58 ` Zhang, Qi Z
2019-03-26 14:02 ` Ananyev, Konstantin
2019-03-26 14:02 ` Ananyev, Konstantin
2019-03-26 14:09 ` Zhang, Qi Z
2019-03-26 14:09 ` Zhang, Qi Z
2019-03-26 14:18 ` Ananyev, Konstantin
2019-03-26 14:18 ` Ananyev, Konstantin
2019-03-27 1:13 ` Zhang, Qi Z
2019-03-27 1:13 ` Zhang, Qi Z
2019-03-27 7:02 ` Zhang, Qi Z
2019-03-27 7:02 ` Zhang, Qi Z
2019-03-22 13:01 ` [dpdk-dev] [PATCH v2 7/7] app/testpmd: verify mtu with rte_eth_dev_info_get() Ian Stokes
2019-03-22 13:01 ` Ian Stokes
2019-03-25 14:20 ` Ferruh Yigit [this message]
2019-03-25 14:20 ` Ferruh Yigit
2019-03-28 16:41 ` Ferruh Yigit
2019-03-28 16:41 ` Ferruh Yigit
2019-03-28 16:43 ` [dpdk-dev] [PATCH v2 0/7] ethdev: add min/max MTU to device info Ferruh Yigit
2019-03-28 16:43 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 1/7] " Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 2/7] net/i40e: set min and max MTU for i40e devices Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 3/7] net/i40e: set min and max MTU for i40e VF devices Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 4/7] net/ixgbe: set min and max MTU for ixgbe devices Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 5/7] net/ixgbe: set min and max MTU for ixgbe VF devices Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 6/7] net/e1000: set min and max MTU for igb devices Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:52 ` [dpdk-dev] [PATCH v3 7/7] app/testpmd: verify MTU with device provided limits Ferruh Yigit
2019-03-29 17:52 ` Ferruh Yigit
2019-03-29 17:56 ` [dpdk-dev] [PATCH v3 1/7] ethdev: add min/max MTU to device info Ferruh Yigit
2019-03-29 17:56 ` Ferruh Yigit
2019-03-29 18:05 ` Ferruh Yigit
2019-03-29 18:05 ` Ferruh Yigit
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=6aa38aa8-5bb3-fee1-0449-c1cc11115a67@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--cc=stephen@networkplumber.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).