From: Yongseok Koh <yskoh@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: Shahaf Shuler <shahafs@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 6/7] net/mlx5: e-switch VXLAN encapsulation rules management
Date: Thu, 25 Oct 2018 00:33:14 +0000 [thread overview]
Message-ID: <20181025003305.GB26874@mtidpdk.mti.labs.mlnx> (raw)
In-Reply-To: <1539612815-47199-7-git-send-email-viacheslavo@mellanox.com>
On Mon, Oct 15, 2018 at 02:13:34PM +0000, Viacheslav Ovsiienko wrote:
> VXLAN encap rules are applied to the VF ingress traffic and have the
> VTEP as actual redirection destinations instead of outer PF.
> The encapsulation rule should provide:
> - redirection action VF->PF
> - VF port ID
> - some inner network parameters (MACs/IP)
> - the tunnel outer source IP (v4/v6)
> - the tunnel outer destination IP (v4/v6). Current
> - VNI - Virtual Network Identifier
>
> There is no direct way found to provide kernel with all required
> encapsulatioh header parameters. The encapsulation VTEP is created
> attached to the outer interface and assumed as default path for
> egress encapsulated traffic. The outer tunnel IP address are
> assigned to interface using Netlink, the implicit route is
> created like this:
>
> ip addr add <src_ip> peer <dst_ip> dev <outer> scope link
>
> Peer address provides implicit route, and scode link reduces
> the risk of conflicts. At initialization time all local scope
> link addresses are flushed from device (see next part of patchset).
>
> The destination MAC address is provided via permenent neigh rule:
>
> ip neigh add dev <outer> lladdr <dst_mac> to <dst_ip> nud permanent
>
> At initialization time all neigh rules of this type are flushed
> from device (see the next part of patchset).
>
> Suggested-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_flow_tcf.c | 394 ++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 389 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_flow_tcf.c b/drivers/net/mlx5/mlx5_flow_tcf.c
> index efa9c3b..a1d7733 100644
> --- a/drivers/net/mlx5/mlx5_flow_tcf.c
> +++ b/drivers/net/mlx5/mlx5_flow_tcf.c
> @@ -3443,6 +3443,376 @@ struct pedit_parser {
> return -err;
> }
>
> +/**
> + * Emit Netlink message to add/remove local address to the outer device.
> + * The address being added is visible within the link only (scope link).
> + *
> + * Note that an implicit route is maintained by the kernel due to the
> + * presence of a peer address (IFA_ADDRESS).
> + *
> + * These rules are used for encapsultion only and allow to assign
> + * the outer tunnel source IP address.
> + *
> + * @param[in] tcf
> + * Libmnl socket context object.
> + * @param[in] encap
> + * Encapsulation properties (source address and its peer).
> + * @param[in] ifindex
> + * Network interface to apply rule.
> + * @param[in] enable
> + * Toggle between add and remove.
> + * @param[out] error
> + * Perform verbose error reporting if not NULL.
> + *
> + * @return
> + * 0 on success, a negative errno value otherwise and rte_errno is set.
> + */
> +static int
> +flow_tcf_rule_local(struct mlx5_flow_tcf_context *tcf,
> + const struct mlx5_flow_tcf_vxlan_encap *encap,
> + unsigned int ifindex,
> + bool enable,
> + struct rte_flow_error *error)
> +{
> + struct nlmsghdr *nlh;
> + struct ifaddrmsg *ifa;
> + alignas(struct nlmsghdr)
> + uint8_t buf[mnl_nlmsg_size(sizeof(*ifa) + 128)];
> +
> + nlh = mnl_nlmsg_put_header(buf);
> + nlh->nlmsg_type = enable ? RTM_NEWADDR : RTM_DELADDR;
> + nlh->nlmsg_flags =
> + NLM_F_REQUEST | (enable ? NLM_F_CREATE | NLM_F_REPLACE : 0);
> + nlh->nlmsg_seq = 0;
> + ifa = mnl_nlmsg_put_extra_header(nlh, sizeof(*ifa));
> + ifa->ifa_flags = IFA_F_PERMANENT;
> + ifa->ifa_scope = RT_SCOPE_LINK;
> + ifa->ifa_index = ifindex;
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_SRC) {
> + ifa->ifa_family = AF_INET;
> + ifa->ifa_prefixlen = 32;
> + mnl_attr_put_u32(nlh, IFA_LOCAL, encap->ipv4.src);
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_DST)
> + mnl_attr_put_u32(nlh, IFA_ADDRESS,
> + encap->ipv4.dst);
> + } else {
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_SRC);
> + ifa->ifa_family = AF_INET6;
> + ifa->ifa_prefixlen = 128;
> + mnl_attr_put(nlh, IFA_LOCAL,
> + sizeof(encap->ipv6.src),
> + &encap->ipv6.src);
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_DST)
> + mnl_attr_put(nlh, IFA_ADDRESS,
> + sizeof(encap->ipv6.dst),
> + &encap->ipv6.dst);
> + }
> + if (!flow_tcf_nl_ack(tcf, nlh, 0, NULL, NULL))
> + return 0;
> + return rte_flow_error_set
> + (error, rte_errno, RTE_FLOW_ERROR_TYPE_UNSPECIFIED, NULL,
> + "netlink: cannot complete IFA request (ip addr add)");
> +}
> +
> +/**
> + * Emit Netlink message to add/remove neighbor.
> + *
> + * @param[in] tcf
> + * Libmnl socket context object.
> + * @param[in] encap
> + * Encapsulation properties (destination address).
> + * @param[in] ifindex
> + * Network interface.
> + * @param[in] enable
> + * Toggle between add and remove.
> + * @param[out] error
> + * Perform verbose error reporting if not NULL.
> + *
> + * @return
> + * 0 on success, a negative errno value otherwise and rte_errno is set.
> + */
> +static int
> +flow_tcf_rule_neigh(struct mlx5_flow_tcf_context *tcf,
> + const struct mlx5_flow_tcf_vxlan_encap *encap,
> + unsigned int ifindex,
> + bool enable,
> + struct rte_flow_error *error)
> +{
> + struct nlmsghdr *nlh;
> + struct ndmsg *ndm;
> + alignas(struct nlmsghdr)
> + uint8_t buf[mnl_nlmsg_size(sizeof(*ndm) + 128)];
> +
> + nlh = mnl_nlmsg_put_header(buf);
> + nlh->nlmsg_type = enable ? RTM_NEWNEIGH : RTM_DELNEIGH;
> + nlh->nlmsg_flags =
> + NLM_F_REQUEST | (enable ? NLM_F_CREATE | NLM_F_REPLACE : 0);
> + nlh->nlmsg_seq = 0;
> + ndm = mnl_nlmsg_put_extra_header(nlh, sizeof(*ndm));
> + ndm->ndm_ifindex = ifindex;
> + ndm->ndm_state = NUD_PERMANENT;
> + ndm->ndm_flags = 0;
> + ndm->ndm_type = 0;
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_DST) {
> + ndm->ndm_family = AF_INET;
> + mnl_attr_put_u32(nlh, NDA_DST, encap->ipv4.dst);
> + } else {
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_DST);
> + ndm->ndm_family = AF_INET6;
> + mnl_attr_put(nlh, NDA_DST, sizeof(encap->ipv6.dst),
> + &encap->ipv6.dst);
> + }
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_ETH_SRC && enable)
> + DRV_LOG(WARNING,
> + "Outer ethernet source address cannot be "
> + "forced for VXLAN encapsulation");
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_ETH_DST)
> + mnl_attr_put(nlh, NDA_LLADDR, sizeof(encap->eth.dst),
> + &encap->eth.dst);
> + if (!flow_tcf_nl_ack(tcf, nlh, 0, NULL, NULL))
> + return 0;
> + return rte_flow_error_set
> + (error, rte_errno, RTE_FLOW_ERROR_TYPE_UNSPECIFIED, NULL,
> + "netlink: cannot complete ND request (ip neigh)");
> +}
> +
> +/**
> + * Manage the local IP addresses and their peers IP addresses on the
> + * outer interface for encapsulation purposes. The kernel searches the
> + * appropriate device for tunnel egress traffic using the outer source
> + * IP, this IP should be assigned to the outer network device, otherwise
> + * kernel rejects the rule.
> + *
> + * Adds or removes the addresses using the Netlink command like this:
> + * ip addr add <src_ip> peer <dst_ip> scope link dev <ifouter>
> + *
> + * The addresses are local to the netdev ("scope link"), this reduces
> + * the risk of conflicts. Note that an implicit route is maintained by
> + * the kernel due to the presence of a peer address (IFA_ADDRESS).
> + *
> + * @param[in] tcf
> + * Libmnl socket context object.
> + * @param[in] vtep
> + * VTEP object, contains rule database and ifouter index.
> + * @param[in] dev_flow
> + * Flow object, contains the tunnel parameters (for encap only).
> + * @param[in] enable
> + * Toggle between add and remove.
> + * @param[out] error
> + * Perform verbose error reporting if not NULL.
> + *
> + * @return
> + * 0 on success, a negative errno value otherwise and rte_errno is set.
> + */
> +static int
> +flow_tcf_encap_local(struct mlx5_flow_tcf_context *tcf,
> + struct mlx5_flow_tcf_vtep *vtep,
> + struct mlx5_flow *dev_flow,
> + bool enable,
> + struct rte_flow_error *error)
> +{
> + const struct mlx5_flow_tcf_vxlan_encap *encap =
> + dev_flow->tcf.vxlan_encap;
> + struct tcf_local_rule *rule;
> + bool found = false;
> + int ret;
> +
> + assert(encap);
> + assert(encap->hdr.type == MLX5_FLOW_TCF_TUNACT_VXLAN_ENCAP);
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_SRC) {
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_DST);
> + LIST_FOREACH(rule, &vtep->local, next) {
> + if (rule->mask & MLX5_FLOW_TCF_ENCAP_IPV4_SRC &&
> + encap->ipv4.src == rule->ipv4.src &&
> + encap->ipv4.dst == rule->ipv4.dst) {
> + found = true;
> + break;
> + }
> + }
> + } else {
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_SRC);
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_DST);
> + LIST_FOREACH(rule, &vtep->local, next) {
> + if (rule->mask & MLX5_FLOW_TCF_ENCAP_IPV6_SRC &&
> + !memcmp(&encap->ipv6.src, &rule->ipv6.src,
> + sizeof(encap->ipv6.src)) &&
> + !memcmp(&encap->ipv6.dst, &rule->ipv6.dst,
> + sizeof(encap->ipv6.dst))) {
> + found = true;
> + break;
> + }
> + }
> + }
> + if (found) {
> + if (enable) {
> + rule->refcnt++;
> + return 0;
> + }
> + if (!rule->refcnt || !--rule->refcnt) {
Same suggestion for this as that of vtep - refcnt handling and adding get()
func.
> + LIST_REMOVE(rule, next);
> + return flow_tcf_rule_local(tcf, encap,
> + vtep->ifouter, false, error);
> + }
> + return 0;
> + }
> + if (!enable) {
> + DRV_LOG(WARNING, "Disabling not existing local rule");
> + rte_flow_error_set
> + (error, ENOENT, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
> + NULL, "Disabling not existing local rule");
> + return -ENOENT;
> + }
> + rule = rte_zmalloc(__func__, sizeof(struct tcf_local_rule),
> + alignof(struct tcf_local_rule));
> + if (!rule) {
> + rte_flow_error_set
> + (error, ENOMEM, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
> + NULL, "unable to allocate memory for local rule");
> + return -rte_errno;
> + }
> + *rule = (struct tcf_local_rule){.refcnt = 0,
> + .mask = 0,
> + };
Is it effective? The allocated memory is already zeroed out.
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_SRC) {
> + rule->mask = MLX5_FLOW_TCF_ENCAP_IPV4_SRC
> + | MLX5_FLOW_TCF_ENCAP_IPV4_DST;
> + rule->ipv4.src = encap->ipv4.src;
> + rule->ipv4.dst = encap->ipv4.dst;
> + } else {
> + rule->mask = MLX5_FLOW_TCF_ENCAP_IPV6_SRC
> + | MLX5_FLOW_TCF_ENCAP_IPV6_DST;
> + memcpy(&rule->ipv6.src, &encap->ipv6.src,
> + sizeof(rule->ipv6.src));
> + memcpy(&rule->ipv6.dst, &encap->ipv6.dst,
> + sizeof(rule->ipv6.dst));
> + }
> + ret = flow_tcf_rule_local(tcf, encap, vtep->ifouter, true, error);
> + if (ret) {
> + rte_free(rule);
> + return ret;
> + }
> + rule->refcnt++;
> + LIST_INSERT_HEAD(&vtep->local, rule, next);
> + return 0;
> +}
> +
> +/**
> + * Manage the destination MAC/IP addresses neigh database, kernel uses
> + * this one to determine the destination MAC address within encapsulation
> + * header. Adds or removes the entries using the Netlink command like this:
> + * ip neigh add dev <ifouter> lladdr <dst_mac> to <dst_ip> nud permanent
> + *
> + * @param[in] tcf
> + * Libmnl socket context object.
> + * @param[in] vtep
> + * VTEP object, contains rule database and ifouter index.
> + * @param[in] dev_flow
> + * Flow object, contains the tunnel parameters (for encap only).
> + * @param[in] enable
> + * Toggle between add and remove.
> + * @param[out] error
> + * Perform verbose error reporting if not NULL.
> + *
> + * @return
> + * 0 on success, a negative errno value otherwise and rte_errno is set.
> + */
> +static int
> +flow_tcf_encap_neigh(struct mlx5_flow_tcf_context *tcf,
> + struct mlx5_flow_tcf_vtep *vtep,
> + struct mlx5_flow *dev_flow,
> + bool enable,
> + struct rte_flow_error *error)
> +{
> + const struct mlx5_flow_tcf_vxlan_encap *encap =
> + dev_flow->tcf.vxlan_encap;
> + struct tcf_neigh_rule *rule;
> + bool found = false;
> + int ret;
> +
> + assert(encap);
> + assert(encap->hdr.type == MLX5_FLOW_TCF_TUNACT_VXLAN_ENCAP);
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_DST) {
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_SRC);
> + LIST_FOREACH(rule, &vtep->neigh, next) {
> + if (rule->mask & MLX5_FLOW_TCF_ENCAP_IPV4_DST &&
> + encap->ipv4.dst == rule->ipv4.dst) {
> + found = true;
> + break;
> + }
> + }
> + } else {
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_SRC);
> + assert(encap->mask & MLX5_FLOW_TCF_ENCAP_IPV6_DST);
> + LIST_FOREACH(rule, &vtep->neigh, next) {
> + if (rule->mask & MLX5_FLOW_TCF_ENCAP_IPV6_DST &&
> + !memcmp(&encap->ipv6.dst, &rule->ipv6.dst,
> + sizeof(encap->ipv6.dst))) {
> + found = true;
> + break;
> + }
> + }
> + }
> + if (found) {
> + if (memcmp(&encap->eth.dst, &rule->eth,
> + sizeof(encap->eth.dst))) {
> + DRV_LOG(WARNING, "Destination MAC differs"
> + " in neigh rule");
> + rte_flow_error_set(error, EEXIST,
> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
> + NULL, "Different MAC address"
> + " neigh rule for the same"
> + " destination IP");
> + return -EEXIST;
> + }
> + if (enable) {
> + rule->refcnt++;
> + return 0;
> + }
> + if (!rule->refcnt || !--rule->refcnt) {
Same suggestion for this as that of vtep - refcnt handling by adding
create()/get()/release() func.
> + LIST_REMOVE(rule, next);
> + return flow_tcf_rule_neigh(tcf, encap,
> + vtep->ifouter,
> + false, error);
> + }
> + return 0;
> + }
> + if (!enable) {
> + DRV_LOG(WARNING, "Disabling not existing neigh rule");
> + rte_flow_error_set
> + (error, ENOENT, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
> + NULL, "unable to allocate memory for neigh rule");
> + return -ENOENT;
> + }
> + rule = rte_zmalloc(__func__, sizeof(struct tcf_neigh_rule),
> + alignof(struct tcf_neigh_rule));
> + if (!rule) {
> + rte_flow_error_set
> + (error, ENOMEM, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
> + NULL, "unadble to allocate memory for neigh rule");
> + return -rte_errno;
> + }
> + *rule = (struct tcf_neigh_rule){.refcnt = 0,
> + .mask = 0,
> + };
Is it effective? The allocated memory is already zeroed out.
> + if (encap->mask & MLX5_FLOW_TCF_ENCAP_IPV4_DST) {
> + rule->mask = MLX5_FLOW_TCF_ENCAP_IPV4_DST;
> + rule->ipv4.dst = encap->ipv4.dst;
> + } else {
> + rule->mask = MLX5_FLOW_TCF_ENCAP_IPV6_DST;
> + memcpy(&rule->ipv6.dst, &encap->ipv6.dst,
> + sizeof(rule->ipv6.dst));
> + }
> + memcpy(&rule->eth, &encap->eth.dst, sizeof(rule->eth));
> + ret = flow_tcf_rule_neigh(tcf, encap, vtep->ifouter, true, error);
> + if (ret) {
> + rte_free(rule);
> + return ret;
> + }
> + rule->refcnt++;
> + LIST_INSERT_HEAD(&vtep->neigh, rule, next);
> + return 0;
> +}
> +
> /* VTEP device list is shared between PMD port instances. */
> static LIST_HEAD(, mlx5_flow_tcf_vtep)
> vtep_list_vxlan = LIST_HEAD_INITIALIZER();
> @@ -3715,6 +4085,7 @@ static LIST_HEAD(, mlx5_flow_tcf_vtep)
> {
> static uint16_t encap_port = MLX5_VXLAN_PORT_RANGE_MIN - 1;
> struct mlx5_flow_tcf_vtep *vtep, *vlst;
> + int ret;
>
> assert(ifouter);
> /* Look whether the attached VTEP for encap is created. */
> @@ -3766,6 +4137,21 @@ static LIST_HEAD(, mlx5_flow_tcf_vtep)
> }
> if (!vtep)
> return 0;
> + /* Create local ipaddr with peer to specify the outer IPs. */
> + ret = flow_tcf_encap_local(tcf, vtep, dev_flow, true, error);
> + if (ret) {
> + if (!vtep->refcnt)
> + flow_tcf_delete_iface(tcf, vtep);
There's no possibility of decreasing vtep->refcnt in flow_tcf_encap_local(),
then why do you expect it to be zero here? If it is already zero at this point,
it should've been deleted when it became zero.
> + return 0;
> + }
> + /* Create neigh rule to specify outer destination MAC. */
> + ret = flow_tcf_encap_neigh(tcf, vtep, dev_flow, true, error);
> + if (ret) {
> + flow_tcf_encap_local(tcf, vtep, dev_flow, false, error);
> + if (!vtep->refcnt)
> + flow_tcf_delete_iface(tcf, vtep);
Same here.
Thanks,
Yongseok
> + return 0;
> + }
> vtep->refcnt++;
> assert(vtep->ifindex);
> return vtep->ifindex;
> @@ -3848,11 +4234,9 @@ static LIST_HEAD(, mlx5_flow_tcf_vtep)
> case MLX5_FLOW_TCF_TUNACT_VXLAN_DECAP:
> break;
> case MLX5_FLOW_TCF_TUNACT_VXLAN_ENCAP:
> -/*
> - * TODO: Remove the encap ancillary rules first.
> - * flow_tcf_encap_neigh(tcf, vtep, dev_flow, false, NULL);
> - * flow_tcf_encap_local(tcf, vtep, dev_flow, false, NULL);
> - */
> + /* Remove the encap ancillary rules first. */
> + flow_tcf_encap_neigh(tcf, vtep, dev_flow, false, NULL);
> + flow_tcf_encap_local(tcf, vtep, dev_flow, false, NULL);
> break;
> default:
> assert(false);
>
next prev parent reply other threads:[~2018-10-25 0:33 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 6:30 [dpdk-dev] [PATCH 1/5] net/mlx5: add VXLAN encap/decap support for e-switch Slava Ovsiienko
2018-10-02 6:30 ` [dpdk-dev] [PATCH 2/5] net/mlx5: e-switch VXLAN netlink routines update Slava Ovsiienko
2018-10-02 6:30 ` [dpdk-dev] [PATCH 3/5] net/mlx5: e-switch VXLAN flow validation routine Slava Ovsiienko
2018-10-02 6:30 ` [dpdk-dev] [PATCH 4/5] net/mlx5: e-switch VXLAN flow translation routine Slava Ovsiienko
2018-10-02 6:30 ` [dpdk-dev] [PATCH 5/5] net/mlx5: e-switch VXLAN tunnel devices management Slava Ovsiienko
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 0/7] net/mlx5: e-switch VXLAN encap/decap hardware offload Viacheslav Ovsiienko
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 1/7] net/mlx5: e-switch VXLAN configuration and definitions Viacheslav Ovsiienko
2018-10-23 10:01 ` Yongseok Koh
2018-10-25 12:50 ` Slava Ovsiienko
2018-10-25 23:33 ` Yongseok Koh
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 2/7] net/mlx5: e-switch VXLAN flow validation routine Viacheslav Ovsiienko
2018-10-23 10:04 ` Yongseok Koh
2018-10-25 13:53 ` Slava Ovsiienko
2018-10-26 3:07 ` Yongseok Koh
2018-10-26 8:39 ` Slava Ovsiienko
2018-10-26 21:56 ` Yongseok Koh
2018-10-29 9:33 ` Slava Ovsiienko
2018-10-29 18:26 ` Yongseok Koh
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 3/7] net/mlx5: e-switch VXLAN flow translation routine Viacheslav Ovsiienko
2018-10-23 10:06 ` Yongseok Koh
2018-10-25 14:37 ` Slava Ovsiienko
2018-10-26 4:22 ` Yongseok Koh
2018-10-26 9:06 ` Slava Ovsiienko
2018-10-26 22:10 ` Yongseok Koh
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 4/7] net/mlx5: e-switch VXLAN netlink routines update Viacheslav Ovsiienko
2018-10-23 10:07 ` Yongseok Koh
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 5/7] net/mlx5: e-switch VXLAN tunnel devices management Viacheslav Ovsiienko
2018-10-25 0:28 ` Yongseok Koh
2018-10-25 20:21 ` Slava Ovsiienko
2018-10-26 6:25 ` Yongseok Koh
2018-10-26 9:35 ` Slava Ovsiienko
2018-10-26 22:42 ` Yongseok Koh
2018-10-29 11:53 ` Slava Ovsiienko
2018-10-29 18:42 ` Yongseok Koh
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 6/7] net/mlx5: e-switch VXLAN encapsulation rules management Viacheslav Ovsiienko
2018-10-25 0:33 ` Yongseok Koh [this message]
2018-10-15 14:13 ` [dpdk-dev] [PATCH v2 7/7] net/mlx5: e-switch VXLAN rule cleanup routines Viacheslav Ovsiienko
2018-10-25 0:36 ` Yongseok Koh
2018-10-25 20:32 ` Slava Ovsiienko
2018-10-26 6:30 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 00/13] net/mlx5: e-switch VXLAN encap/decap hardware offload Slava Ovsiienko
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 01/13] net/mlx5: prepare makefile for adding e-switch VXLAN Slava Ovsiienko
2018-11-01 20:33 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 02/13] net/mlx5: prepare meson.build " Slava Ovsiienko
2018-11-01 20:33 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 03/13] net/mlx5: add necessary definitions for " Slava Ovsiienko
2018-11-01 20:35 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 04/13] net/mlx5: add necessary structures " Slava Ovsiienko
2018-11-01 20:36 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 05/13] net/mlx5: swap items/actions validations for e-switch rules Slava Ovsiienko
2018-11-01 20:37 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 06/13] net/mlx5: add e-switch VXLAN support to validation routine Slava Ovsiienko
2018-11-01 20:49 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 07/13] net/mlx5: add VXLAN support to flow prepare routine Slava Ovsiienko
2018-11-01 21:03 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 08/13] net/mlx5: add VXLAN support to flow translate routine Slava Ovsiienko
2018-11-01 21:18 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 09/13] net/mlx5: e-switch VXLAN netlink routines update Slava Ovsiienko
2018-11-01 21:21 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 10/13] net/mlx5: fix e-switch Flow counter deletion Slava Ovsiienko
2018-11-01 22:00 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 11/13] net/mlx5: add e-switch VXLAN tunnel devices management Slava Ovsiienko
2018-11-01 23:59 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 12/13] net/mlx5: add e-switch VXLAN encapsulation rules Slava Ovsiienko
2018-11-02 0:01 ` Yongseok Koh
2018-11-01 12:19 ` [dpdk-dev] [PATCH v3 13/13] net/mlx5: add e-switch VXLAN rule cleanup routines Slava Ovsiienko
2018-11-02 0:01 ` Yongseok Koh
2018-11-01 20:32 ` [dpdk-dev] [PATCH v3 00/13] net/mlx5: e-switch VXLAN encap/decap hardware offload Yongseok Koh
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 " Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 01/13] net/mlx5: prepare makefile for adding E-Switch VXLAN Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 00/13] net/mlx5: e-switch VXLAN encap/decap hardware offload Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 01/13] net/mlx5: prepare makefile for adding E-Switch VXLAN Slava Ovsiienko
2018-11-12 20:01 ` [dpdk-dev] [PATCH 0/4] net/mlx5: prepare to add E-switch rule flags check Slava Ovsiienko
2018-11-12 20:01 ` [dpdk-dev] [PATCH 1/4] net/mlx5: prepare Netlink communication routine to fix Slava Ovsiienko
2018-11-13 13:21 ` Shahaf Shuler
2018-11-12 20:01 ` [dpdk-dev] [PATCH 2/4] net/mlx5: fix Netlink communication routine Slava Ovsiienko
2018-11-13 13:21 ` Shahaf Shuler
2018-11-14 12:57 ` Slava Ovsiienko
2018-11-12 20:01 ` [dpdk-dev] [PATCH 3/4] net/mlx5: prepare to add E-switch rule flags check Slava Ovsiienko
2018-11-12 20:01 ` [dpdk-dev] [PATCH 4/4] net/mlx5: add E-switch rule hardware offload flag check Slava Ovsiienko
2018-11-13 13:21 ` [dpdk-dev] [PATCH 0/4] net/mlx5: prepare to add E-switch rule flags check Shahaf Shuler
2018-11-14 14:56 ` Shahaf Shuler
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 03/13] net/mlx5: add necessary definitions for E-Switch VXLAN Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 02/13] net/mlx5: prepare meson.build for adding " Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 04/13] net/mlx5: add necessary structures for " Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 05/13] net/mlx5: swap items/actions validations for E-Switch rules Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 06/13] net/mlx5: add E-Switch VXLAN support to validation routine Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 07/13] net/mlx5: add VXLAN support to flow prepare routine Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 08/13] net/mlx5: add VXLAN support to flow translate routine Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 09/13] net/mlx5: update E-Switch VXLAN netlink routines Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 10/13] net/mlx5: fix E-Switch Flow counter deletion Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 11/13] net/mlx5: add E-switch VXLAN tunnel devices management Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 12/13] net/mlx5: add E-Switch VXLAN encapsulation rules Slava Ovsiienko
2018-11-03 6:18 ` [dpdk-dev] [PATCH v5 13/13] net/mlx5: add E-switch VXLAN rule cleanup routines Slava Ovsiienko
2018-11-04 6:48 ` [dpdk-dev] [PATCH v5 00/13] net/mlx5: e-switch VXLAN encap/decap hardware offload Shahaf Shuler
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 02/13] net/mlx5: prepare meson.build for adding E-Switch VXLAN Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 03/13] net/mlx5: add necessary definitions for " Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 04/13] net/mlx5: add necessary structures " Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 05/13] net/mlx5: swap items/actions validations for E-Switch rules Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 07/13] net/mlx5: add VXLAN support to flow prepare routine Slava Ovsiienko
2018-11-02 21:38 ` Yongseok Koh
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 06/13] net/mlx5: add E-Switch VXLAN support to validation routine Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 08/13] net/mlx5: add VXLAN support to flow translate routine Slava Ovsiienko
2018-11-02 21:53 ` Yongseok Koh
2018-11-02 23:29 ` Yongseok Koh
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 09/13] net/mlx5: update E-Switch VXLAN netlink routines Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 10/13] net/mlx5: fix E-Switch Flow counter deletion Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 11/13] net/mlx5: add E-switch VXLAN tunnel devices management Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 12/13] net/mlx5: add E-Switch VXLAN encapsulation rules Slava Ovsiienko
2018-11-02 17:53 ` [dpdk-dev] [PATCH v4 13/13] net/mlx5: add E-switch VXLAN rule cleanup routines Slava Ovsiienko
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=20181025003305.GB26874@mtidpdk.mti.labs.mlnx \
--to=yskoh@mellanox.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=viacheslavo@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).