From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
"matana@mellanox.com" <matana@mellanox.com>
Cc: Asaf Penso <asafp@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: support adding a new UDP tunnel
Date: Wed, 4 Sep 2019 14:46:04 +0000 [thread overview]
Message-ID: <AM4PR05MB326592A4AE0920DA7C880B7ED2B80@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1566468943-30201-1-git-send-email-rasland@mellanox.com>
> -----Original Message-----
> From: Raslan Darawsheh <rasland@mellanox.com>
> Sent: Thursday, August 22, 2019 13:16
> To: Slava Ovsiienko <viacheslavo@mellanox.com>; matana@mellanox.com
> Cc: Asaf Penso <asafp@mellanox.com>; dev@dpdk.org
> Subject: [PATCH] net/mlx5: support adding a new UDP tunnel
>
> This adds support for adding a new udp tunnel port on a specific vxlan types.
>
> currently we only support vxlan, vxlan-gpe on ports 4789, 4790 respectivly.
> without having to configure anything in the NIC.
>
> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> drivers/net/mlx5/mlx5.c | 26 ++++++++++++++++++++++++++
> drivers/net/mlx5/mlx5.h | 2 ++
> 2 files changed, 28 insertions(+)
>
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c index
> 962c0d5..dc7b10b 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -745,6 +745,31 @@ mlx5_free_verbs_buf(void *ptr, void *data
> __rte_unused) }
>
> /**
> + * DPDK callback to add udp tunnel port
> + *
> + * @param[in] dev
> + * A pointer to eth_dev
> + * @param[in] udp_tunnel
> + * A pointer to udp tunnel
> + *
> + * @return
> + * 0 on valid udp ports and tunnels, -ENOTSUP otherwise.
> + */
> +int
> +mlx5_udp_tunnel_port_add(struct rte_eth_dev *dev __rte_unused,
> + struct rte_eth_udp_tunnel *udp_tunnel) {
> + assert(udp_tunnel != NULL);
> + if (udp_tunnel->prot_type == RTE_TUNNEL_TYPE_VXLAN &&
> + udp_tunnel->udp_port == 4789)
> + return 0;
> + if (udp_tunnel->prot_type == RTE_TUNNEL_TYPE_VXLAN_GPE &&
> + udp_tunnel->udp_port == 4790)
> + return 0;
> + return -ENOTSUP;
> +}
> +
> +/**
> * Initialize process private data structure.
> *
> * @param dev
> @@ -962,6 +987,7 @@ const struct eth_dev_ops mlx5_dev_ops = {
> .rx_queue_intr_enable = mlx5_rx_intr_enable,
> .rx_queue_intr_disable = mlx5_rx_intr_disable,
> .is_removed = mlx5_is_removed,
> + .udp_tunnel_port_add = mlx5_udp_tunnel_port_add,
> };
>
> /* Available operations from secondary process. */ diff --git
> a/drivers/net/mlx5/mlx5.h b/drivers/net/mlx5/mlx5.h index f559f83..fda9f5d
> 100644
> --- a/drivers/net/mlx5/mlx5.h
> +++ b/drivers/net/mlx5/mlx5.h
> @@ -674,6 +674,8 @@ int64_t mlx5_get_dbr(struct rte_eth_dev *dev,
> struct mlx5_devx_dbr_page **dbr_page); int32_t
> mlx5_release_dbr(struct rte_eth_dev *dev, uint32_t umem_id,
> uint64_t offset);
> +int mlx5_udp_tunnel_port_add(struct rte_eth_dev *dev,
> + struct rte_eth_udp_tunnel *udp_tunnel);
>
> /* mlx5_ethdev.c */
>
> --
> 2.7.4
next prev parent reply other threads:[~2019-09-04 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 10:15 Raslan Darawsheh
2019-09-04 14:46 ` Slava Ovsiienko [this message]
2019-09-05 10:37 ` Raslan Darawsheh
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=AM4PR05MB326592A4AE0920DA7C880B7ED2B80@AM4PR05MB3265.eurprd05.prod.outlook.com \
--to=viacheslavo@mellanox.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matana@mellanox.com \
--cc=rasland@mellanox.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).