DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Doherty, Declan" <declan.doherty@intel.com>
To: Sharmila Podury <sharmila.podury@gmail.com>
Cc: dev@dpdk.org, Sharmila Podury <sharmila.podury@att.com>
Subject: Re: [dpdk-dev] [PATCH] net/bonding: add ethdev ops function for MTU set
Date: Tue, 9 Jan 2018 15:32:33 +0000	[thread overview]
Message-ID: <680ceda0-3474-bcfe-bd28-de99d8ac5243@intel.com> (raw)
In-Reply-To: <20180104063443.1821-1-sharmila.podury@gmail.com>

On 04/01/2018 6:34 AM, Sharmila Podury wrote:
> From: Sharmila Podury <sharmila.podury@att.com>
> 
> Set the MTU for bonding device by calling .mtu_set for all
> the slaves. Set the MTU only if all slaves support .mtu_set,
> and there is no error returned from any slave.
> 
> Signed-off-by: Sharmila Podury <sharmila.podury@att.com>
> ---
>   drivers/net/bonding/rte_eth_bond_pmd.c | 31 ++++++++++++++++++++++++++++++-
>   1 file changed, 30 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
> index fe2328954..183bdbafc 100644
> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
> @@ -2707,6 +2707,34 @@ bond_ethdev_rss_hash_conf_get(struct rte_eth_dev *dev,
>   	return 0;
>   }
>   
> +static int
> +bond_ethdev_mtu_set(struct rte_eth_dev *dev, uint16_t mtu)
> +{
> +	struct rte_eth_dev *slave_eth_dev;
> +	struct bond_dev_private *internals = dev->data->dev_private;
> +	int ret, i;
> +
> +	rte_spinlock_lock(&internals->lock);
> +
> +	for (i = 0; i < internals->slave_count; i++) {
> +		slave_eth_dev = &rte_eth_devices[internals->slaves[i].port_id];
> +		if (*slave_eth_dev->dev_ops->mtu_set == NULL) {
> +			rte_spinlock_unlock(&internals->lock);
> +			return -ENOTSUP;
> +		}
> +	}
> +	for (i = 0; i < internals->slave_count; i++) {
> +		ret = rte_eth_dev_set_mtu(internals->slaves[i].port_id, mtu);
> +		if (ret < 0) {
> +			rte_spinlock_unlock(&internals->lock);
> +			return ret;
> +		}
> +	}
> +
> +	rte_spinlock_unlock(&internals->lock);
> +	return 0;
> +}
> +
>   const struct eth_dev_ops default_dev_ops = {
>   	.dev_start            = bond_ethdev_start,
>   	.dev_stop             = bond_ethdev_stop,
> @@ -2726,7 +2754,8 @@ const struct eth_dev_ops default_dev_ops = {
>   	.reta_update          = bond_ethdev_rss_reta_update,
>   	.reta_query           = bond_ethdev_rss_reta_query,
>   	.rss_hash_update      = bond_ethdev_rss_hash_update,
> -	.rss_hash_conf_get    = bond_ethdev_rss_hash_conf_get
> +	.rss_hash_conf_get    = bond_ethdev_rss_hash_conf_get,
> +	.mtu_set              = bond_ethdev_mtu_set
>   };
>   
>   static int
> 

Acked-by: Declan Doherty <declan.doherty@intel.com>

       reply	other threads:[~2018-01-09 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180104063443.1821-1-sharmila.podury@gmail.com>
2018-01-09 15:32 ` Doherty, Declan [this message]
2018-01-10 20:42   ` Ferruh Yigit
2018-01-11  3:31     ` Chas Williams
2018-01-11 19:12 Sharmila Podury
2018-01-11 20:14 ` 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=680ceda0-3474-bcfe-bd28-de99d8ac5243@intel.com \
    --to=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=sharmila.podury@att.com \
    --cc=sharmila.podury@gmail.com \
    /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).