DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
	arybchenko@solarflare.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] librte_net: define TCP flags in rte_tcp.h instead of in rte_eth_ctrl.h
Date: Mon, 13 May 2019 13:54:39 +0200	[thread overview]
Message-ID: <20190513115439.5fjarh6au7u64fmq@platinum> (raw)
Message-ID: <20190513115439.S-wexp1BQWhcpAD1JaruGqakycA3EwUSFI-8q49_4hA@z> (raw)
In-Reply-To: <1557509654-19325-1-git-send-email-mb@smartsharesystems.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 5471 bytes --]

Hi Morten,

On Fri, May 10, 2019 at 07:34:14PM +0200, Morten Brørup wrote:
> TCP flags were moved to the TCP header file from the Ethernet control
> header file, keeping their names intact.
> 
> Missing TCP ECN flags were added.
> 
> The ALL mask did not include TCP ECN flags, so it was renamed to reflect
> that it applies to N-tuple filtering only.
> A driver using the ALL mask was updated accordingly.
> 
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> ---
>  app/test-pmd/cmdline.c           |    4 ++--
>  drivers/net/e1000/igb_ethdev.c   |    8 ++++----
>  lib/librte_ethdev/rte_eth_ctrl.h |    8 +-------
>  lib/librte_net/rte_tcp.h         |   13 +++++++++++++
>  4 files changed, 20 insertions(+), 13 deletions(-)
> 
> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
> index ee50e45..59a45c1 100644
> --- a/app/test-pmd/cmdline.c
> +++ b/app/test-pmd/cmdline.c
> @@ -9983,7 +9983,7 @@ cmd_2tuple_filter_parsed(void *parsed_result,
>  			" when protocol is TCP.\n");
>  		return;
>  	}
> -	if (res->tcp_flags_value > TCP_FLAG_ALL) {
> +	if (res->tcp_flags_value > RTE_NTUPLE_TCP_FLAGS_MASK) {
>  		printf("invalid TCP flags.\n");
>  		return;
>  	}
> @@ -10141,7 +10141,7 @@ cmd_5tuple_filter_parsed(void *parsed_result,
>  			" when protocol is TCP.\n");
>  		return;
>  	}
> -	if (res->tcp_flags_value > TCP_FLAG_ALL) {
> +	if (res->tcp_flags_value > RTE_NTUPLE_TCP_FLAGS_MASK) {
>  		printf("invalid TCP flags.\n");
>  		return;
>  	}
> diff --git a/drivers/net/e1000/igb_ethdev.c b/drivers/net/e1000/igb_ethdev.c
> index b897e8a..c2fe19a 100644
> --- a/drivers/net/e1000/igb_ethdev.c
> +++ b/drivers/net/e1000/igb_ethdev.c
> @@ -3702,7 +3702,7 @@ ntuple_filter_to_2tuple(struct rte_eth_ntuple_filter *filter,
>  		return -EINVAL;
>  	if (filter->priority > E1000_2TUPLE_MAX_PRI)
>  		return -EINVAL;  /* filter index is out of range. */
> -	if (filter->tcp_flags > TCP_FLAG_ALL)
> +	if (filter->tcp_flags > RTE_NTUPLE_TCP_FLAGS_MASK)
>  		return -EINVAL;  /* flags is invalid. */
>  
>  	switch (filter->dst_port_mask) {
> @@ -3782,7 +3782,7 @@ igb_inject_2uple_filter(struct rte_eth_dev *dev,
>  		ttqf &= ~E1000_TTQF_MASK_ENABLE;
>  
>  	/* tcp flags bits setting. */
> -	if (filter->filter_info.tcp_flags & TCP_FLAG_ALL) {
> +	if (filter->filter_info.tcp_flags & RTE_NTUPLE_TCP_FLAGS_MASK) {
>  		if (filter->filter_info.tcp_flags & TCP_URG_FLAG)
>  			imir_ext |= E1000_IMIREXT_CTRL_URG;
>  		if (filter->filter_info.tcp_flags & TCP_ACK_FLAG)
> @@ -4188,7 +4188,7 @@ ntuple_filter_to_5tuple_82576(struct rte_eth_ntuple_filter *filter,
>  		return -EINVAL;
>  	if (filter->priority > E1000_2TUPLE_MAX_PRI)
>  		return -EINVAL;  /* filter index is out of range. */
> -	if (filter->tcp_flags > TCP_FLAG_ALL)
> +	if (filter->tcp_flags > RTE_NTUPLE_TCP_FLAGS_MASK)
>  		return -EINVAL;  /* flags is invalid. */
>  
>  	switch (filter->dst_ip_mask) {
> @@ -4318,7 +4318,7 @@ igb_inject_5tuple_filter_82576(struct rte_eth_dev *dev,
>  	imir |= filter->filter_info.priority << E1000_IMIR_PRIORITY_SHIFT;
>  
>  	/* tcp flags bits setting. */
> -	if (filter->filter_info.tcp_flags & TCP_FLAG_ALL) {
> +	if (filter->filter_info.tcp_flags & RTE_NTUPLE_TCP_FLAGS_MASK) {
>  		if (filter->filter_info.tcp_flags & TCP_URG_FLAG)
>  			imir_ext |= E1000_IMIREXT_CTRL_URG;
>  		if (filter->filter_info.tcp_flags & TCP_ACK_FLAG)
> diff --git a/lib/librte_ethdev/rte_eth_ctrl.h b/lib/librte_ethdev/rte_eth_ctrl.h
> index 5ea8ae2..f21e84b 100644
> --- a/lib/librte_ethdev/rte_eth_ctrl.h
> +++ b/lib/librte_ethdev/rte_eth_ctrl.h
> @@ -184,13 +184,7 @@ struct rte_eth_syn_filter {
>  		RTE_NTUPLE_FLAGS_DST_PORT | \
>  		RTE_NTUPLE_FLAGS_PROTO)
>  
> -#define TCP_URG_FLAG 0x20
> -#define TCP_ACK_FLAG 0x10
> -#define TCP_PSH_FLAG 0x08
> -#define TCP_RST_FLAG 0x04
> -#define TCP_SYN_FLAG 0x02
> -#define TCP_FIN_FLAG 0x01
> -#define TCP_FLAG_ALL 0x3F
> +#define RTE_NTUPLE_TCP_FLAGS_MASK 0x3F /**< TCP flags filter can match. */
>  
>  /**
>   * A structure used to define the ntuple filter entry
> diff --git a/lib/librte_net/rte_tcp.h b/lib/librte_net/rte_tcp.h
> index 91f5898..2e89b5e 100644
> --- a/lib/librte_net/rte_tcp.h
> +++ b/lib/librte_net/rte_tcp.h
> @@ -2,6 +2,7 @@
>   * Copyright(c) 1982, 1986, 1990, 1993
>   *      The Regents of the University of California.
>   * Copyright(c) 2010-2014 Intel Corporation.
> + * Copyright(c) 2019 SmartShare Systems.
>   * All rights reserved.
>   */
>  

IMHO, adding the copyright for flags move is a bit overkill.

> @@ -35,6 +36,18 @@ struct tcp_hdr {
>  	uint16_t tcp_urp;   /**< TCP urgent pointer, if any. */
>  } __attribute__((__packed__));
>  
> +/**
> + * TCP Flags
> + */
> +#define TCP_CWR_FLAG 0x80 /**< Congestion Window Reduced */
> +#define TCP_ECE_FLAG 0x40 /**< ECN-Echo */
> +#define TCP_URG_FLAG 0x20 /**< Urgent Pointer field significant */
> +#define TCP_ACK_FLAG 0x10 /**< Acknowledgment field significant */
> +#define TCP_PSH_FLAG 0x08 /**< Push Function */
> +#define TCP_RST_FLAG 0x04 /**< Reset the connection */
> +#define TCP_SYN_FLAG 0x02 /**< Synchronize sequence numbers */
> +#define TCP_FIN_FLAG 0x01 /**< No more data from sender */
> +
>  #ifdef __cplusplus
>  }
>  #endif

Moving these flags in rte_tcp.h makes sense.

But I think they will need to be renamed with a RTE_ prefix inside this
patchset: https://patches.dpdk.org/patch/52556/
So we need to take care to the dependency between these 2 patchsets.

Acked-by: Olivier Matz <olivier.matz@6wind.com>

  parent reply	other threads:[~2019-05-13 11:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 17:34 Morten Brørup
2019-05-10 17:34 ` Morten Brørup
2019-05-13 11:54 ` Olivier Matz [this message]
2019-05-13 11:54   ` Olivier Matz
2019-05-13 13:02   ` Morten Brørup
2019-05-13 13:02     ` Morten Brørup
2019-05-13 14:47     ` Stephen Hemminger
2019-05-13 14:47       ` Stephen Hemminger
2019-05-13 15:15       ` Morten Brørup
2019-05-13 15:15         ` Morten Brørup
2019-05-13 17:00         ` Ferruh Yigit
2019-05-13 17:00           ` Ferruh Yigit
  -- strict thread matches above, loose matches on Subject: below --
2019-05-10 17:10 Morten Brørup
2019-05-10 17:10 ` Morten Brørup
2019-05-10 16:10 Morten Brørup
2019-05-10 16:10 ` Morten Brørup
2019-05-10 14:10 Morten Brørup
2019-05-10 14:10 ` Morten Brørup

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=20190513115439.5fjarh6au7u64fmq@platinum \
    --to=olivier.matz@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=mb@smartsharesystems.com \
    --cc=thomas@monjalon.net \
    /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).