[v2] sched : Initialize tc ov watermark.

Message ID 20210309161002.31384-1-savinay.dharmappa@intel.com (mailing list archive)
State Superseded, archived
Delegated to: Thomas Monjalon
Headers
Series [v2] sched : Initialize tc ov watermark. |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/iol-intel-Performance success Performance Testing PASS
ci/travis-robot success travis build: passed
ci/github-robot success github build: passed
ci/Intel-compilation success Compilation OK
ci/iol-testing success Testing PASS
ci/intel-Testing success Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-mellanox-Functional success Functional Testing PASS

Commit Message

Savinay Dharmappa March 9, 2021, 4:10 p.m. UTC
  tc ov watermark is initialized with computed value of
max tc ov watermark.

Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
---
v2: fix spelling error. 
---
 lib/librte_sched/rte_sched.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
  

Comments

Jasvinder Singh March 10, 2021, 4:53 p.m. UTC | #1
> -----Original Message-----
> From: Dharmappa, Savinay <savinay.dharmappa@intel.com>
> Sent: Tuesday, March 9, 2021 4:10 PM
> To: Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; dev@dpdk.org
> Cc: Dharmappa, Savinay <savinay.dharmappa@intel.com>
> Subject: [PATCH v2] sched : Initialize tc ov watermark.
> 
> tc ov watermark is initialized with computed value of max tc ov watermark.
> 
> Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
> ---
> v2: fix spelling error.
> ---
>  lib/librte_sched/rte_sched.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/librte_sched/rte_sched.c b/lib/librte_sched/rte_sched.c index
> 7c56880681..cd87e688e4 100644
> --- a/lib/librte_sched/rte_sched.c
> +++ b/lib/librte_sched/rte_sched.c
> @@ -1249,7 +1249,6 @@ rte_sched_subport_config(struct rte_sched_port
> *port,  #ifdef RTE_SCHED_SUBPORT_TC_OV
>  		/* TC oversubscription */
>  		s->tc_ov_wm_min = port->mtu;
> -		s->tc_ov_wm = s->tc_ov_wm_max;
>  		s->tc_ov_period_id = 0;
>  		s->tc_ov = 0;
>  		s->tc_ov_n = 0;
> @@ -1277,6 +1276,7 @@ rte_sched_subport_config(struct rte_sched_port
> *port,  #ifdef RTE_SCHED_SUBPORT_TC_OV
>  		s->tc_ov_wm_max = rte_sched_time_ms_to_bytes(profile-
> >tc_period,
>  							s-
> >pipe_tc_be_rate_max);
> +		s->tc_ov_wm = s->tc_ov_wm_max;
>  #endif
>  		s->profile = subport_profile_id;
> 
> --
> 2.17.1

Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
  
Coyle, David March 15, 2021, 4:42 p.m. UTC | #2
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Savinay Dharmappa
> Sent: Tuesday, March 9, 2021 4:10 PM
> To: Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; dev@dpdk.org
> Cc: Dharmappa, Savinay <savinay.dharmappa@intel.com>
> Subject: [dpdk-dev] [PATCH v2] sched : Initialize tc ov watermark.
> 
> tc ov watermark is initialized with computed value of max tc ov watermark.
> 
> Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
> ---
> v2: fix spelling error.
> ---
>  lib/librte_sched/rte_sched.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Tested-by: David Coyle <david.coyle@intel.com>
  
Thomas Monjalon March 23, 2021, 4:02 p.m. UTC | #3
09/03/2021 17:10, Savinay Dharmappa:
> tc ov watermark is initialized with computed value of
> max tc ov watermark.

Sorry I don't understand what the change is doing.
Was there an issue?

In the title, please avoid "tc ov" which is meaningless
for most of readers I guess.

> --- a/lib/librte_sched/rte_sched.c
> +++ b/lib/librte_sched/rte_sched.c
> -		s->tc_ov_wm = s->tc_ov_wm_max;
[...]
> +		s->tc_ov_wm = s->tc_ov_wm_max;
  
Thomas Monjalon April 20, 2021, 10:13 a.m. UTC | #4
Ping

23/03/2021 17:02, Thomas Monjalon:
> 09/03/2021 17:10, Savinay Dharmappa:
> > tc ov watermark is initialized with computed value of
> > max tc ov watermark.
> 
> Sorry I don't understand what the change is doing.
> Was there an issue?
> 
> In the title, please avoid "tc ov" which is meaningless
> for most of readers I guess.
  
Jasvinder Singh April 20, 2021, 10:36 a.m. UTC | #5
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, April 20, 2021 11:14 AM
> To: Dharmappa, Savinay <savinay.dharmappa@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] sched : Initialize tc ov watermark.
> 
> Ping
> 
> 23/03/2021 17:02, Thomas Monjalon:
> > 09/03/2021 17:10, Savinay Dharmappa:
> > > tc ov watermark is initialized with computed value of max tc ov
> > > watermark.
> >
> > Sorry I don't understand what the change is doing.
> > Was there an issue?
> >
> > In the title, please avoid "tc ov" which is meaningless for most of
> > readers I guess.
> 
> 
Hi Thomas,

This is a fix for oversubscription threshold value of traffic class which is computed later. We will re-spin the patch by mentioning "fix" in the message and title.

Thanks,
Jasvinder
  
Thomas Monjalon April 20, 2021, 1:54 p.m. UTC | #6
20/04/2021 12:36, Singh, Jasvinder:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 
> > Ping
> > 
> > 23/03/2021 17:02, Thomas Monjalon:
> > > 09/03/2021 17:10, Savinay Dharmappa:
> > > > tc ov watermark is initialized with computed value of max tc ov
> > > > watermark.
> > >
> > > Sorry I don't understand what the change is doing.
> > > Was there an issue?
> > >
> > > In the title, please avoid "tc ov" which is meaningless for most of
> > > readers I guess.
> > 
> > 
> Hi Thomas,
> 
> This is a fix for oversubscription threshold value of traffic class which is computed later. We will re-spin the patch by mentioning "fix" in the message and title.

Yes please give a clear explanation with full words, thanks.
  

Patch

diff --git a/lib/librte_sched/rte_sched.c b/lib/librte_sched/rte_sched.c
index 7c56880681..cd87e688e4 100644
--- a/lib/librte_sched/rte_sched.c
+++ b/lib/librte_sched/rte_sched.c
@@ -1249,7 +1249,6 @@  rte_sched_subport_config(struct rte_sched_port *port,
 #ifdef RTE_SCHED_SUBPORT_TC_OV
 		/* TC oversubscription */
 		s->tc_ov_wm_min = port->mtu;
-		s->tc_ov_wm = s->tc_ov_wm_max;
 		s->tc_ov_period_id = 0;
 		s->tc_ov = 0;
 		s->tc_ov_n = 0;
@@ -1277,6 +1276,7 @@  rte_sched_subport_config(struct rte_sched_port *port,
 #ifdef RTE_SCHED_SUBPORT_TC_OV
 		s->tc_ov_wm_max = rte_sched_time_ms_to_bytes(profile->tc_period,
 							s->pipe_tc_be_rate_max);
+		s->tc_ov_wm = s->tc_ov_wm_max;
 #endif
 		s->profile = subport_profile_id;