DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Július Milan" <jmilan.dev@gmail.com>, dev@dpdk.org, jgrajcia@cisco.com
Subject: Re: [dpdk-dev] [PATCH] net/memif: add dev_link info
Date: Tue, 4 Feb 2020 12:09:17 +0000	[thread overview]
Message-ID: <beb57ee2-3df2-0597-15af-94e134d905d2@intel.com> (raw)
In-Reply-To: <20200204113024.GA16593@vbox>

On 2/4/2020 11:30 AM, Július Milan wrote:
> This information is useful or needed for user applications as t-rex.
> 
> Signed-off-by: Július Milan <jmilan.dev@gmail.com>
> ---
>  drivers/net/memif/rte_eth_memif.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/net/memif/rte_eth_memif.c b/drivers/net/memif/rte_eth_memif.c
> index 8dd1d0d63..27c0f0924 100644
> --- a/drivers/net/memif/rte_eth_memif.c
> +++ b/drivers/net/memif/rte_eth_memif.c
> @@ -52,6 +52,13 @@ static const char * const valid_arguments[] = {
>  	NULL
>  };
>  
> +static const struct rte_eth_link pmd_link = {
> +	.link_speed = ETH_SPEED_NUM_10G,
> +	.link_duplex = ETH_LINK_FULL_DUPLEX,
> +	.link_status = ETH_LINK_DOWN,
> +	.link_autoneg = ETH_LINK_AUTONEG
> +};
> +
>  #define MEMIF_MP_SEND_REGION		"memif_mp_send_region"
>  
>  
> @@ -1488,6 +1495,7 @@ memif_create(struct rte_vdev_device *vdev, enum memif_role_t role,
>  	data = eth_dev->data;
>  	data->dev_private = pmd;
>  	data->numa_node = numa_node;
> +	data->dev_link = pmd_link;
>  	data->mac_addrs = ether_addr;
>  
>  	eth_dev->dev_ops = &ops;
> 

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

  reply	other threads:[~2020-02-04 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 11:30 Július Milan
2020-02-04 12:09 ` Ferruh Yigit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-04 10:47 Július Milan

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=beb57ee2-3df2-0597-15af-94e134d905d2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jgrajcia@cisco.com \
    --cc=jmilan.dev@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).